I succesfully created my first Collaboration between Portal and ArcGIS online - I can see the FL in the AGO folder but I get an error whenever I try to add it to a map:
https:// ... /FeatureServer?f=json status: 504
I thought status 504 was generic for a timeout?
there are several layers in the FL I'm sharing and I'm not above splitting them into smaller groups or even publishing one at a time if that's what it takes ... thoughts?
update: I see an error that I may have missed on the initial post: when accessing the FL on AGOL, I'm prompted to sign into portal but no matter what creds I enter I get the error: unable to access the authentication service
Hello @wilcow ,
Hope you are keeping safe and well. I would like to request you the following details in order to understand more in regards to the issue and probably figure out the root cause.
We can try to figure out the cause of this once the above is clear.
-Archit
hi there @ArchitSrivastava,
thanks for the response!
thanks again for the response - I'll keep you posted
Hello @wilcow ,
Apologies for delayed update. I checked the logs you shared and it seems you are getting a CORS error while trying to communicate between AGOL and ArcGIS Enterprise as attached.
Hence, I would like you to have a look at the articles below:
https://enterprise.arcgis.com/en/portal/latest/administer/windows/restrict-cross-domain-requests-to-... (could not find the 10.6.1 documentation, looking for it)
Additionally, when I asked "authentication", what I was referring to was the authentication for Portal and ArcGIS Online, is it Portal security or Integrated Windows Authentication(for Portal) or SAML or any other way.
Furthermore, could you share a screenshot of "console" tab while performing the layer sharing process. This will show us where the CORS is originating from and where it's getting blocked.
Hope it helps!
-Archit
OK thanks for the feedback @ArchitSrivastava
For authentication on the Portal, we use SAML (from our on-premise Active Directory) with a single identity provider.
Re: your request for a screenshot - I kept developer tools open while I built a new collaboration and saw no messages until I tried to open the synced layer in AGOL. I've attached the screen shot below. Hope this is what you needed
thanks again for you help
I have been experiencing similar issues. Unfortunately I haven't figured them all out yet either. I have noticed that when I change the sharing in Portal on the item the rest service in manager doesn't get the same sharing. So the item moves but when you try to use it AGOL needs to ask for credentials and the access is not the same.
The second thing to check is that you allow portal access in your AGOL Organization Security Settings. I don't think it will totally help but should allow AGOL to log into Portal when you get the prompt.
We have a colaboration set up using references and whenever anyone in Enterprise shares a layer with the group at that end of the colab it shows up in the AGOL group as my item since I set up the colab. Then I have to share that item in AGOL around. It is kind of a pain.
Hello @JosephRathvon ,
That sure is an interesting approach to get around the situation. I do agree with you that "Allow Portal Access" should not be impacting this process as long as it's not needed, perhaps this would shed some more light:
Additionally, I think a better approach here would be to utilize "Manual Sync"(Document below) option from Portal Admin.
The workflow I am suggesting is to switch the Portal logs to DEBUG (Please note these are disk consuming files, do switch them back to the logging level they were before), perform a manual Sync and go over the logs to understand which step seems to be causing an issue.
https://developers.arcgis.com/rest/users-groups-and-items/sync.htm
Hopefully this will allow us to narrow down the cause of the problem.
-Archit