Skip to main content
New Participant
August 16, 2016
Answered

Unable to authorize access because the client configuration is invalid: invalid_request

  • August 16, 2016
  • 5 replies
  • 10364 views

I'm trying to get the access token for my OAuth application. I've followed the documentation and created an application, and navigated to the URL:

https://secure.na1.echosign.com/public/oauth?redirect_uri=[REDIRECT URL]&response_type=code&client_id=[CLIENT ID]&scope=agreement_read:account

From my understanding it's supposed to bring me to a page where I click 'Allow' and then I get redirected to the redirect URL with parameters in the URL. But instead I get "Unable to authorize access because the client configuration is invalid: invalid_request".

I'm not sure what I'm missing or doing wrong here, my redirect URL is the exact same, and my Client ID is the exact same and the scope is correct.

I've looked at this forum topic:

Help with OAuth2

And it mentions code on the user's side, do I need to have my own code on my redirect URL to do something here?

This topic has been closed for replies.
Correct answer Meenakshi Negi

Hi Pawanm,

Sorry for the delay in response.

I have checked your account with the email address that you have used for the forums.

You have a free developer account for Adobe Sign.

The settings are not enabled by default to access the Integration Key in the free Developer account.

I would recommend you contact Pre-Sales team to get the settings enabled.

They will be able to provide pre-sales technical assistance to you.

Please refer to this link Adobe Sign plans for individuals and businesses | Adobe Document Cloud to get in contact with them.

Let us know if you need any help from us.

Regards,

Meenakshi

5 replies

dominikb1322602
New Participant
April 25, 2018

I solved this problem by adding my redirect-url to the OAuth settings. It's pretty unhandy for development since you have to provide a HTTPS enabled domain ...

New Participant
July 22, 2020

I was able to trace my problem to the echosign server I was using. 

When you're working in your development account setting up your application look at the URL to identify which server you're on.  I am on secure.na2.echosign.com and I should use that domain when requesting my OAuth code.  While the Getting Started Guide will tell you to send the request to https://secure.echosign.com/public/oauth? in my case I had to send it to https://secure.na2.echosign.com/public/oauth? to get a valid response.  Evidently development accounts are setup on specific servers and the OAuth authentication doesn't work across them.

New Participant
October 25, 2020

Where exactly does it say which server that you're on? I can't find na/eu/any indicator anywhere

New Participant
December 5, 2017

Same issue here. I have both scopes set in the OAuth settings: user_login = self and agreement_send = account.

I also notice that the examples use a short client_id, e.g. "d4HQNPFIXFD255H", but my client_id is longer, e.g. "d4HQNPFIXFD255H-1234abcdefGHIJKLMNO". Am I looking at the wrong thing?

kwangheey64222055
New Participant
June 27, 2017

I have same program. Is there any update from adobe?

New Participant
June 7, 2017

Same problem here. Any news on this from Adobe ?

Community Manager
August 16, 2016

Hello Owen,

Make sure to provide the same scopes in the authorization url as per the application created. Also, if issue persists, please inbox me the registered email address, application and the complete authorization url created at your end.

Thanks,

-Rijul

New Participant
July 20, 2018

I am facing same issue , after adding same scope and redirect URL also.

Any suggestions ??

Thanks in advance

Community Manager
April 17, 2019

Hey Pawanm,

We are facing the same issues while creating a API request. Its our trial account. The API URL is: Message and the error message is https://secure.echosign.com/public/oauth?redirect_uri=https://www.softobiz.com&response_type=code&client_id=CBJCHBCAABAAC2-G54nOzbnbeigKJdpIObBAdzmlKkPq&scope=agreement_read:account

As we are following the same recommended steps from the official documentation.

We will appreciate if you look into the same and guide us accordingly.

Thanks,
Rajbir


you sign account will be on a specific server, for example secure.eu1.echosign.com or secure.in1.echosign.com

this needs to be reflected in the Oauth end point. The oauth documentation Adobe Sign, an Adobe Document Cloud Solution ,

may not be pointing to the same shard as you account.

So instead of pointing to

https://secure.eu1.echosign.com/public/oauth?

you may need to update this to

https://secure.na2.echosign.com/public/oauth?