Skip to main content
S
st93711675
Participating Frequently
March 31, 2026
Question

What changes are required to OAuth configuration if the domain of the urls change, for eg. previously it was 123.abc.com and now it is 123.xyz.com.

  • March 31, 2026
  • 1 reply
  • 48 views

Ours is an ASP.Net web application having PARTNER integration with AdobeSign. I have configured OAuth for the application with a list of Redirect URLs and Scope etc. All working well for many years.

Question - what do I need to do if the domain of the urls change, for eg. previously it was 123.abc.com and now it is 123.xyz.com. Do I need to make any additional changes to the configuration other than adding the new URLs in the redirect url list. Any help would be appreciated.

 

    1 reply

    Souvik Sadhu
    Community Manager
    Souvik SadhuCommunity Manager
    Community Manager
    April 1, 2026

    HI @st93711675,


    Hope you are doing well. Thanks for writing in!


    When your domain changes (e.g., https://adobe.ly/4v5WmHs > https://adobe.ly/3PHirMx), OAuth with Acrobat Sign is sensitive to exact URL matching, especially for redirect URIs.

    Below is what you need to update and verify.


    Add the new Redirect URI(s)

    In your Adobe Sign OAuth application:

    • Add all new URLs using the new domain: https://adobe.ly/4m4YkUr

    • Keep the old URLs temporarily if both domains are still in use

    Important: Redirect URIs must match exactly (protocol, domain, path, trailing slash).

    Info here: Migrating from https://adobe.ly/4cjCkSA to https://adobe.ly/4bKcjM2


    Update Redirect URI in your https://adobe.ly/4vaCSlo app

    Ensure your application code is using the new domain:

    • Authorization request (redirect_uri parameter)

    • Token exchange request

    If your app still sends redirect_uri=https://adobe.ly/4cj3VTV... OAuth will fail even if the new domain is registered.


    Check hardcoded domain references

    Search your application for:

    • Absolute URLs

    • Config files (web.config / appsettings.json)

    • Environment variables

    Update all references from: https://adobe.ly/4v5WmHs > https://adobe.ly/3PHirMx

    Info here: Enable single sign-on with SAML


    Session / Cookie considerations

    If your OAuth flow depends on session state:

    • Cookies tied to https://adobe.ly/4v5FAbI will not work on https://adobe.ly/4djlFj7

    • Users may need to log in again after the domain change


    Update any Webhook / Callback URLs (if used)

    If you are using Adobe Sign webhooks:

    • Update webhook endpoints to the new domain

    • Re-register them if required


    Let us know how it goes.


    Regards,

    Souvik

    S
    st93711675Author
    Participating Frequently
    April 2, 2026

    Thank you Souvik for a quick and detailed response!

    I have verified the following suggestions.

    1. Add the new Redirect URI(s)
    2. Update Redirect URI in your app
    3. Check hardcoded domain references
    4. Session / Cookie considerations
    5. Update any Webhook / Callback URLs (if used) - Not applicable in our case

    Just FYI that the application users have their own account with AdobeSign and the application can authenticate users across multiple Adobe Sign customer accounts.

    New domain URIs have been added in the list of Redirect URIs and the application reads redirect_uri from document.URL, logic that has been working well for many years.

    We are trying to identify if there needs to be additional action taken by us (the application owner) or the customers/users when the url domain changes.

    Two additional questions -

    1. Do the customer/user accounts have to do anything on their end when the application url domain changes? We are noticing a weird behavior with their tokens that we are trying to identify if its related to the application url domain change.
    2. What about the internal test users (whose email changed due to domain change) that are part of the application owner domain. We are noticing that the internal users can no longer use their email account to test the integration.

    Also, is there a way to talk to someone in Support to get help on this.

    Meenakshi0101
    Community Manager
    Meenakshi0101Community Manager
    Community Manager
    April 13, 2026

    Hi st93711675,

     

    We are sorry for the delay in response.

     

    We checked your account linked to your community profile and confirmed that you are using the Acrobat Sign Developer service.

     

    Since you have a question regarding the Acrobat Sign integration feature, we recommend reaching out to the experts for the most accurate information. If you have an Acrobat Sign Enterprise plan, please contact our Adobe Sign Enterprise support team. You can find the contact steps in the following help document:: https://helpx.adobe.com/sign/using/adobesign-support-resources.html.

     

    For inquiries related to the developer account, please contact our pre-sales team. They can provide pre-sales technical assistance and the correct information. You can reach them through this page: https://business.adobe.com/products/sign-solutions.html.

     

    Let us know if you have any questions.

     

    Thanks,

    Meenakshi

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices