Participant

Answered

Error-"Unable to authorize access because the client configuration is invalid: invalid_request".

Forum|Forum|6 years ago
November 4, 2019
5 replies
10237 views

I'm trying to integrate Adobe Sign into our application. I found a step-by-step manual to do this (https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/gstarted.md).

So, I created an Application and configured OAuth access for it. I configured my application to handle HTTPS requests. I created a request to get the access token according to the documentation, and used the appropriate Client ID and redirect URI, but I got an error message: "Unable to authorize access because the client configuration is invalid: invalid_request".

The problem could be that it runs on my development machine which is not accessible from internet. I tried to use tools such as ngrok, Serveo or Pagekite that redirect the requests from outside to a local PC, but it still dosn't work.

Can you advise me how to solve this issue, please? Thanks in advance.

This topic has been closed for replies.

Correct answer SimonESATS

I take it the dev account was sorted?

When logging in the Sign webportal, pay attention to which shard you are and which domain is being used.

for example a typical login doman is https://secure.eu1.adobesign.com

this needs to be used when making the first GET call to get the Oauth grant code, using the abve exammple EU1 is the shrd and adobesign.com is the domain.

Also this page has the better documentation: https://secure.na1.adobesign.com/public/static/oauthDoc.jsp

(again make a note of the shard) and also a note of the actual endpoint:

/public/oauth/v2

N

nurkassym_sndk

Participant

I followed the guide as well, but I'm still getting an error.
I checked the redirect_url, the shard where I created the account, and the application, but I still can't get the code.

My account was created at the following URL: https://secure.na3.adobesign.com/

I'm sending the request to the same URL: https://secure.na3.adobesign.com/public/oauth/v2?redirect_uri={my_url}&response_type=code&client_id={...

Am I doing something wrong?

I was able to get the authorization page once, but that's not even the code.

D

defaultcrud3z737hhv

Participant

I've copied the URL from the docs here:

https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/gstarted/get_access_token.md

https://secure.adobesign.com/public/oauth?
redirect_uri=https://myserver.com&
response_type=code&
client_id=CBAThIsIsNoTaReAlmPBvPF&
scope=user_login:self+agreement_send:account

and replaced the values for redirect_uri and client_id with the values from my API Application, but no matter what I try I keep getting this error:

There's lots of other posts about this but no clear resolution that I can find. I have triple checked my scopes and the redirect uri and client id and they are all correct. Not sure what else to try at this point?

S

SimonESATSCorrect answer

Adobe Employee

I take it the dev account was sorted?

When logging in the Sign webportal, pay attention to which shard you are and which domain is being used.

for example a typical login doman is https://secure.eu1.adobesign.com

this needs to be used when making the first GET call to get the Oauth grant code, using the abve exammple EU1 is the shrd and adobesign.com is the domain.

Also this page has the better documentation: https://secure.na1.adobesign.com/public/static/oauthDoc.jsp

(again make a note of the shard) and also a note of the actual endpoint:

/public/oauth/v2

D

defaultcrud3z737hhv

Participant

Thanks for your reply - I've managed to resolve this now using the correct shard/domain for my account. I also did get my dev account sorted here.

It could be made clearer in the docs about the need to identify your shard/domain. For example I was using the Getting Started guide here and it just says to "First, copy and paste the following URL" which uses an invalid URL it seems.

Many thanks for your help.

K

Kalyani Wani

Participant

I'm trying to get the Authorization code to generate Access token, the following is the URL that I'm using

https://secure.na1.echosign.com/public/oauth?redirect_uri=https://www.google.co.in&response_type=code&client_id={ClientID}&scope=user_login:self+agreement_send:account

When I run the following URL in the browser it is throwing the following error -

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

Can anyone help me?

Thank you in advance.

Meenakshi Negi

Community Manager

Hi Kalyani,

Thank you for reaching out.

I have checked your account with the email address used to sign in to the community. You have a free developer account for Adobe Sign.

Please try updating the URL for authentication from https: //secure.na1.adobesign.com/public/oauth? to https: //secure.in1.echosign.com/public/oauth? in the URL.

If that doesn't resolve the issue, I would recommend you contact the Pre-Sales team. They will be able to provide pre-sales technical assistance to you.

Please use the contact us button under the Adobe Sign for business and enterprise in this link https://www.adobe.com/sign/pricing/plans.html to get in contact with them.

Let us know if you need any help from us.

Thanks,

Meenakshi

K

Kalyani Wani

Participant

Hi Meenakshi,

Thank you for your immediate response, the solution that you told worked, and I was able to retrieve "Authorization Code".

R

reto3Author

Participant

Okay, I found the solution myself: I didn't use the correct shard. I send my requests to URL https://secure.echosign.com/public/oauth. After I posted my message, I was shown some similar issues and there I noticed I have to use the shard as well. But it's not mentioned in the "Get started" guide (https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/gstarted/get_access_token.md)

C

Coastal360788632jqi

Participant

how can we find what the shard is for the application that we are setting up? im trying to use integromat but i cant find this information in their help center and Adobe just says that each clients will be different? i dont understand why this is so difficult.

Meenakshi Negi

Community Manager

Hi Coastal360788632jqi,

Thank you for reaching out.

If you are looking for the shard information, you may try https://secure.na4.echosign.com/public/oauth?. If you are looking for some other information, let us know what exactly you are trying.

Thanks,

Meenakshi

Marking a reply or response “Correct” will help future users with the same issue quickly identify the correct answer.

F

felixOvianet

Participant

Hi,

Following the documentation: https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/gstarted/get_access_token.md

I wasn't able to get an access Token.

I tried :

https://secure.echosign.com/public/oauth?redirect_uri=https://www.ovianet.com/web/&response_type=code&client_id=CBJCHBCAABAAhAlPBqP3HT-zOXPLym5WAOaX2m1lx8zr&scope=user_login:self+agreement_send:account

and :

https://secure.eu1.echosign.com/public/oauth?redirect_uri=https%3A%2F%2Fwww.ovianet.com%2Fweb%2FoauthDemo&response_type=code&client_id=CBJCHBCAABAAhAlPBqP3HT-zOXPLym5WAOaX2m1lx8zr&scope=user_login:self+agreement_write:account

But the answer of the webservice always is:

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

What must I do?

Regards,

Felix

F

felixOvianet

Participant

Well... I had to set the redirect_uri in my console panel too! Too bad it's not written anywhere... Would have saved me hours.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded