Set your SAML Mode settings in Acrobat Sign to SAML Allowed
- Verify that you know your native Acrobat Sign password
- This is a precaution to avoid being accidentally locked out of your account after you change the IdP
What's New
Get Started
Administer
Send, Sign, and Manage Agreements
Advanced Agreement Capabilities and Workflows
Integrate with other products
Acrobat Sign Developer
Support and Troubleshooting
Adobe Acrobat Sign has deployed a new domain: adobesign.com.
Customers can identify their domain by logging in to Acrobat Sign and checking the URL:
If your URL reads documents.adobe.com, your domain is not changing. However, customers will need to explicitly allow email from adobesign@adobesign.com
To ensure continuity of service, customers should prepare for the domain migration by reviewing the below list of actions and addressing the issues that are germane for their account.
All impacted accounts will have the ability to switch to the new domain once their account has successfully resolved any concerns/tasks that the below list prompts.
Changing your SAML configuration requires that you opt-in to the new domain immediately after saving the new IdP settings in Acrobat Sign.
SSO to the account will be broken until the domain switch is completed.
If you are a SAML using customer, be sure to set your SAML Mode settings in Acrobat Sign to SAML Allowed
All accounts are strongly encouraged to "opt-in" to the new domain as early as possible to allow time for troubleshooting if problems arise.
Accounts can switch back to the legacy domain if problems do occur.
When you are satisfied that your account is ready to migrate:
Log in to Acrobat Sign as an account-level administrator
Navigate to Account > Account Settings > Account Setup
Click the Update now button
A check list of the important actions is presented in an overlay.
Review each point and check them off when you are confident the concern is properly addressed for your account.
Click OK when all of the boxes are checked, and then click Save:
Bookmarks to the old domain (echosign.com) can prompt multiple Cookie enablement requests when the login process shifts the user to the new domain (adobesign.com).
It is recommended that users be notified to update their bookmarks to target the new login domain.
If you have to revert back to the legacy domain for any reason, the process is the same as the initial switch.
Log in to Acrobat Sign as an account-level administrator
Navigate to Account > Account Settings > Account Setup
Click the Update now button, and then click Save
Below you will find a list of common questions about the domain migration.
If you can not find an answer for your question here, please contact your success manager or customer support.
The domain in the sample response, points to adobesign.com even if the request was made from echosign.com.
Case: Account migrated to adobesign.com domain - API call made using adobesign.com domain
1 2 3 4 |
{ "apiAccessPoint": "https://api.na2.adobesign.com/", "webAccessPoint": "https://secure.na2.adobesign.com/" } |