Can't set up Authorization Request

[Bewitched_ninja0448]

Hello,

basically I have Account #1 on "shard" na3, this account has the Adobe Acrobat Pro license and is being used to send signatures.

Then I have Account #2 on "shard" na4, this account is a Adobe Sign Developer Account.

I want to send a HTTP requests to my Application ID on Account #2 to send signatures. I am trying to get the Authorization Request for Account #1, this way I have access to my documents, templates etc on Account #1.

API documentation tells me to use this structured URL to process the Authorization and get the Token Code. 

https://secure.na4.adobesign.com/public/oauth/v2?redirect_uri=https://example.com/oauthDemo&
response_type=code&client_id=d4HQNPFIXFD255H&scope=user_login:self+agreement_write:account&
state=S6YQD7KDA556DIV6NAU4ELTGSIV26ZNMXDSF7WIEEP0ZLQCLDQ89OYG78C3K9SROC8DXCGRVSGKU1IT1

 This structured URL is working great with Account #2 but when I try to use it on Account #1 it returns invalid request error. It seems the issue is that my Application ID is on "shard" na4 while Account #1 is on "shard" na3.

I have tried using "https://secure.na3.adobesign.com/public/oauth/v2?" without luck, keep getting same error. 

Sometimes I am sent to a log in page and then sends me to https://acrobat.adobe.com/link/home/

I just cant Authorize and give permissions using my Account #1.

[Bewitched_ninja0448]

Following the https://secure.na1.adobesign.com/public/oauthDemo I found that:

https://approperty.na3.documents.adobe.com/public/oauth/v2?redirect_uri=https%3A%2F%2Fsecure.na1.echosign.com%2Fpublic%2FoauthDemo&response_type=code&client_id=9MEJXY4Y4R7L2T&scope=agreement_write&state=XWX1CX1944U799AU4U13Start&dc_remove=true

Is working well. I tried using that structured URL and replaced my client_id, redirect_uri and scope but it is giving me the same invalid request.

[S. S · Accepted solution]

Hi @Bewitched_ninja0448,

Hope you are doing well. Thanks for writing in!

The core of your problem is that Adobe Sign OAuth authorization must happen on the same shard (data center) where both the account and the registered application exist, but in your setup:

• Account #1 → shard na3 → where your docs/templates live.

• Application ID (developer app) → shard na4.

That’s why the OAuth handshake works for Account #2 (also na4) but fails for Account #1 — the OAuth service in na3 doesn’t recognize an application registered in na4.

Adobe Sign apps are shard-bound. An app created in the na4 developer portal is not visible to the na3 API endpoints. When you try using https://adobe.ly/4lzv7iP with an na4 app ID, the server says invalid_request because that client_idis unknown in na3’s database.

This is what you can try:

• Log in to Account #1’s Adobe Sign API applications page (on the na3 shard).

• Create a new application with the same redirect URI and scopes.

• Use this app’s client_id and client_secret when hitting https://adobe.ly/45hsX2m.

• This way, OAuth authorization happens fully within na3.

Let me know if this helps.

Regards,
Souvik.