Just stood up a development instance of Portal 10.6. Trying to add items from secured services. It picks up that they are secured, but the option to store credentials is not there for us. Can't imagine this functionality is no longer there, so I'm wondering if anyone else has seen this behavior, or can direct me to where this option is now if it has changed. The documentation seems to say that it should be there, so maybe our install of Enterprise didn't fully work?
Solved! Go to Solution.
That behavior normally points to Portal not trusting the certificate that is used for HTTPS on the secured service. There's a call to the checkUrl.jsp page that determines if Portal trusts the resource it's connecting to:
Ex.
https://portal.domain.com/portal/sharing/checkUrl.jsp?url=<url>
You can try this manually and see if it goes through. If you see a failed response, then it's likely that the certificate isn't trusted. You can follow the link below to trust the certificate used for the secure service:
That behavior normally points to Portal not trusting the certificate that is used for HTTPS on the secured service. There's a call to the checkUrl.jsp page that determines if Portal trusts the resource it's connecting to:
Ex.
https://portal.domain.com/portal/sharing/checkUrl.jsp?url=<url>
You can try this manually and see if it goes through. If you see a failed response, then it's likely that the certificate isn't trusted. You can follow the link below to trust the certificate used for the secure service:
Thanks Jonathan -
That did the trick. We have applied new certificates to our ArcServer machines, and did not get them loaded into this Portal instance.