Request an Authorization Code: /auth: Bad Request

Request an Authorization Code: /auth: Bad Request

When using the /auth API call, I consistently receive "Bad Request".  This happens when pasting the URL provided at http://software.intel.com/en-us/articles/cloud-services-intel-identity-s... (with substitutions) directly into my web browser, or when sending it from a .NET test app.

Here's the exact URL I'm using (client_id masked):

https://api.intel.com/identityui/v2/auth?state=786773836763&redirect_uri...

From other activity here, it appears that the API responds differently for other people.

-Glen

16 post / 0 nuovi
Ultimo contenuto
Per informazioni complete sulle ottimizzazioni del compilatore, consultare l'Avviso sull'ottimizzazione

Like Glen, I receive a "Bad Request" response when requesting an auth token in my web browser and iOS device.

I have to amend this. I was able to get past this error condition, but only in sync mode. Attempting to use async mode, by setting the redirect URL to urn:intel:identity:oauth:oob:async still fails with Bad Request.

Ritratto di norman-chou (Intel)

Are you using DevTest or Production client id/secret key?

Citazione:

norman-chou (Intel) ha scritto:

Are you using DevTest or Production client id/secret key?

I have two apps set up. The one that fails async is devtest.

Ritratto di norman-chou (Intel)

Can you try using this call back URI: urn:intel:identity:oauth:oob:async

From what I can gather, it appears you are doing a desktop app.

Ritratto di norman-chou (Intel)

If you are using devtest key, you need to make call to the devtest api.

In this case https://api.intel.com:8081/....

If you are using the production key you want to use this url: https://api.intel.com/....

Ritratto di norman-chou (Intel)

This issue has been resolved, the root cause was the need to point to the devtest api when using devtest client id/secret key.

Citazione:

norman-chou (Intel) ha scritto:

Can you try using this call back URI: urn:intel:identity:oauth:oob:async

From what I can gather, it appears you are doing a desktop app.

No go. If I use that URL I get Bad Request. If I try to set it as the redirect URL on the app config page, it says it updated but it does not change. Other URLs are accepted without issue.

Does async mode auth work at all?

I was able to update the redirect URL to urn:intel:identity:oauth:oob:async this morning, so apparently whatever was up with that is fixed.  Now I'm able to get a reasonable response from /auth with response_type=code.

However, /authcode returns "Not Found".

Additionally, if I "steal" the code=* argument (which I suspect is not the code I want, but do not know) from the redirect call to auth.yourid.intel.com/facebook/callback, and use it to call /token, I get Bad Request.

Ritratto di PONRAM

dont use directly on your web broweser try to make test with a simple app

pointing it to the devtest api resolved the issue.

john

I'm having the same problem as described above however pointing to the devtest api does not resolve the issue. In fact, I don't even get to the authorization token request if I point to devtest. It tells me my initial authentication request is a Bad Request. When pointing to the production API I at least get past that point. I cannot get an authorization token no matter how many ways I've tried. It keeps telling me I have an "invalid_request".

Really in need of some fast help from Intel as the app I'm developing is for Intel (our client) at an event this week.

Investigating in the case, we will contact you soon.

Luis M.

70799

 

No worries Luis. I was in contact with another developer at Intel over the phone this weekend who helped me sort everything out.

Thanks!

MR

Ritratto di Dmitry Oganezov (Intel)

Just an idea - do you use JavaScript SDK? If so, do you use iframes?

Accedere per lasciare un commento.