Issues with Adobe Sign Okta app and migrating to new domain adobesign.com

[Alex5E59]

Hello.

We have followed the steps to migrate the new Okta Adobe Sign app from echosign.com to the new domain adobesign.com ( (https://helpx.adobe.com/sign/using/echosign-domain-change.html) but no success. Adobe Sign support is telling us now that the Okta Adobe Sign app available in the Okta marketplace is the problem!?   Did Adobe Sign team verify this at all!?

Anyone having similar issues?

Thanks,

[Enrique5D1E]

I recently updated to the adobesign.com domain and are having the same issue where the SSO with Okta is not functioning correctly. When a user attemps to sign in using corporate credentials (SSO), it goes out to Okta and shows it is signing in use the Adobe Provisioning app in Okta, and then just takes them back to the login screen. I have worked with our security team to try finding out the problem, but based on all documentation, we have the SAML settings in Adobe Sign and the Okta Adobe Sign Provisioning set up correctly.

Have you gotten an anwer on this yet?

[Alex5E59]

I had to work with Adobe support since their instructions do not work as intended with the current Okta Adobe Sign app in the Okta store.

We ended up creating a new app from scratch in Okta and then following the Adobe instructions. The one caveat is on the Adobe Sign end, you have to use the full URL for the Entity ID/Issuer URL:

Hope this helps.