Hi Community,
I have a 3rd-party Map Image Layer stored as a portal item with its credentials also stored (Portal 10.9.1). When I open the URL provided on the item detail page, it leads me to the service endpoint page saying "Services Directory has been disabled. Error: 403". The URL follows such pattern "https://my.gisportal.com/portal/sharing/rest/{portalitemID}/rest/services/{ServiceName}/MapServer". I also noticed that when accessing this URL, I have been logged in as "portaladmin" instead of the stored credential account I initially applied to the item.
I can confirm that neither of my portal sharing rest endpoint nor my server rest endpoint have been disabled.
However, the same service stored as a portal item in our legacy portal (Portal 10.5.1) works quite well. The rest URL "https://legacy.gisportal.com/portal/sharing/rest/{portalitemID}/rest/services/{ServiceName}/MapServe..." can be accessed. When accessed, the logged in user appears as the stored credential account.
Just wondering if I am missing any setting here?
Best regards,
Anbin
Solved! Go to Solution.
Hi,
I have done further investigation and I found that it is not any version specific issue.
Depending on the authentication method, if it is SAML or built-in user, when accessing the rest endpoint of the secured service, the portal/sharing page won't automatically log in. Hence, needs to add token to the URL.
It was working in our older portal because the portal was configured with IWA, hence the user was automatically logged into the rest endpoint.
Thanks all,
Anbin
Hi SIT,
I have tested, and don't think it is the cause of the issue. Incognito mode still leads to the same issue.
Regards,
Hi,
I have done further investigation and I found that it is not any version specific issue.
Depending on the authentication method, if it is SAML or built-in user, when accessing the rest endpoint of the secured service, the portal/sharing page won't automatically log in. Hence, needs to add token to the URL.
It was working in our older portal because the portal was configured with IWA, hence the user was automatically logged into the rest endpoint.
Thanks all,
Anbin