Help with OAuth2

[CJackMithy]

We have an internal WPF application which needs to use the EchoSign functionality. Basically, the application will send some letters which needs to be e signed by an external user.

I’ve created the EchoSign developer account and added an application under the “All Applications” section.

I'm stuck with the OAuth step. When I replace just the client_id in the OAuth demo  ( https://secure.echosign.com/public/oauthDemo ) with my application’s client_id, I get the following error message

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

Am I missing anything ? Also, I notice that the below OAuth query requires a  redirect_uri parameter. What would be the value in my case as it’s an internal WPF application ?

https://secure.echosign.com/public/oauth?
redirect_uri=https://secure.echosign.com/public/oauthDemo&
response_type=code&client_id=9MEJXY4Y4R7L2T&scope=agreement_send

Thanks

[himanshuc53017295]

I am stuck there, deadend at the start of project. Did anyone got this working. I am getting "Unable to authorize access because the client configuration is invalid: invalid_request" error.

[guillaumef17837650]

same for us

[guillaumef17837650]

Adobe support response endpoint error so !

Original URL (from documentation) : https://secure.echosign.com/public/oauth?

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

How to get your endpoint ?

On your dashboard :

[mattrosenblatt]

Have there been any updates to this? I've been banging my head against the wall for hours trying to figure out why this thing isn't working at all. I keep getting invalid_request, and it looks like the documentation is likely incorrect as there's a large influx of people reporting this same problem.

[luisi29937925]

Your right!, you saved my day, thanks!

[hrvojek91097807]

Having the same issue "invalid_request" .. always

[derrickm17458635]

@

25. Re: Help with OAuth2

hrvojek91097807

make sure you dont have spaces after & on your request.

[shashidharc35017311]

I have same story - Unable to authorize access because the client configuration is invalid: invalid_request

[srikarm]

Hi All,

Noticed that many people reported this issue and I too was under the same impression that this API request never worked going through this thread, until I did some additional research.

As someone in this thread mentioned, make sure you are using the correct endpoint url : https://secure.<your_region>.echosign.com//public/oauth

Next navigate to your Adobe eSign developer account -> Adobe Sign API -> API Application -> Select the Application you already setup for current integration -> Configure OAuth for Application -> Under Configure OAuth section -> Enabled Scopes -> Make sure all the scope values you provide in your API call matches exactly with the scopes (user_read) enabled here with exact same modifier (Self/ Account/ group).

If you are running into Unable to authorize access because the client configuration is invalid: invalid_request - fixing scopes & modifiers in url as per the Application API should resolve the issue following above steps.

Summary of items to verify:

URL

Scope & Modifier values in Application API

Also make sure redirect_uri doesn't have any parameters in the url itself. The above URL only accepts parameters that are expected in the API request.

Thanks

Srikar

[j11711451]

IMPORTANT: Adobe's documentation tells you to "copy and paste the following URL", but if you paste it into a text editor to make the indicated modifications, the URL will actually be wrong, because the text they tell you to copy and paste has spaces in it to indent the later lines. It looks like a typical copy-able code block that you would see in tutorials on any developer site, where the visual formatting doesn't match what gets copied (raw text), but it's not 😕

To fix this, do the following:

1. Copy and paste the URI into a text editor

2. Change the values for redirect_uri and client_id

3. Manually delete all of the white space/carriage returns so that the text is on a single line

4. Paste the modified URI into your browser

[rpurushotma1]

I noticed the client ID in the post you made was "9MEJXY4Y4R7L2T"

I originally used:

https://secure.na2.echosign.com/public/oauth?redirect_uri=https://www.swirlystudios.com/esign/check_...

and got the same error message. I then used the full client_id and it worked:

https://secure.na2.echosign.com/public/oauth?redirect_uri=https://www.swirlystudios.com/esign/check_...

[MaxNev]

Got same issue, newly registered app (tried two different).

Dev account, also have paid user account for client (not enterprise).

Tried different scopes (just simply leave one user_login:self), different datacenters.

Everything i got is:

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

Anybody have solution for that?
Do i/client need enterprise account to make signed pdf?

[slideshowp2]

before:

https://secure.na1.echosign.com/public/oauth?redirect_uri=https://www.github.com/mrdulin&response_ty...

after:

https://secure.na2.echosign.com/public/oauth?redirect_uri=https://www.github.com/mrdulin&response_ty...

the only change part is the region.

[alvarom1614094]

Thank you!

[rashtekar]

Was anyone finally got this working? I have exact same problem with my free developer instance. I have correct redirect_url configured and also enabled all scopes just to make this work but no luck

[jorgey87267153]

el problema es la url que se copia, primero si estan desarrollando reemplacen la url base con la url del sition donde se creo la cuenta, el resto es tal como dice el manual, recuerden en los ambitos enviar los mismos o configurar los mismos para que no tengan problemas, cualquier cosa distinta indica error de configuracion

[Groaker]

Hi everyone,

I managed to solve the "invalid request" issue thanks to many of the right answers given above.

There is one info though I think was crucial which was not given here and i think that was the piece missing.

I wanted to take some time to sumup the right clues.

- The URL format

As some mentionned, build your request string in Notepad to make sure you have no line break or space

- The region for the "secure" part of URL

https://secure.jp1.echosign.com/public/oauth

I am in Japan so it was JP1 for me. This is not written in the documentation.

If like me you dont know what is your Region code here, here is how to find it out. Login to your adobeSIgn dev account (where you created your AdobeSign application) and look at the URL in your browser. There it is! you will see your region code written in the browser url.

- The ClientID

Also refered as ApplicationID, copy and paste the whole ID. Yes, the loooong one.

- The redirect_uri

     - If you dont have a website yet, yes Google is fine for now: https://www.google.com

     - Now very important, make sure that https://www.google.com (or whatever yours is) is also the same one written in the [Configure OAuth] section of your application! so that both request and application configure matches.

In your request, to match the configuration screen

redirect_uri=https://www.google.com

- The scopes!

As couple of people nicely said it, both your request string AND your application checked scopes MUST match.

So, for example here was my test application scopes

Only user_login:self is checked

So your request MUST be: scope=user_login:self

- Important: Being loggedin in your account during the execution of the url

Now, is time to paste your URL. I dont know if the following is relevant but by doing so along with couple of changes above it worked so just in case i am adding this here! it doesnt take time and its another assurance for you.

     - Open a new tab

     - Log in to your AdobeSign account life if you wanted to create an app

     - Now logged in, on same page in this tab now paste your URL in the browser.

     - Tadaaa !! Now i got finally the "allow access" screen to get the authorization code!

I think I covered all you need to know above. I cant think of anything else.I personaly think that for some people here, request uri mismatch, region in url miss was the main bottle neck.

Groaker

[roaned25239202]

Groaker​, thanks this is critical information that adobe seems to have forgotten to mention...

[andresb66741419]

i had the same issue, just go to you're account and look the region that the account uses, in my case it uses na2 https://secure.na2.echosign.com/account/home, and add the region to the url request

it should look like this

Provided by adobe : https://secure.echosign.com/public/oauth?redirect_uri=https://example.com/oauthDemo&

response_type=code&client_id=d4HQNPFIXFD255H&scope=user_login:self+agreement_send:account&

state=S6YQD7KDA556DIV6NAU4ELTGSIV26ZNMXDSF7WIEEP0ZLQCLDQ89OYG78C3K9SROC8DXCGRVSGKU1IT1

With region change: https://secure.na2.echosign.com/public/oauth?redirect_uri=https://example.com/oauthDemo&

response_type=code&client_id=d4HQNPFIXFD255H&scope=user_login:self+agreement_send:account&

state=S6YQD7KDA556DIV6NAU4ELTGSIV26ZNMXDSF7WIEEP0ZLQCLDQ89OYG78C3K9SROC8DXCGRVSGKU1IT1