redirect url: urn:ietf:wg:oauth:2.0:oob

[ooga]

Hi,

I'm developing a stand along application in a proprietary language, and looking at the docs, it says to setup the redirect to be urn:ietf:wg:oauth:2.0:oob, but when I try doing that I get an error it tells me:

Redirect URL "urn:ietf:wg:oauth:2.0:oob" is not allowed for this type of OAuth 2 client.

maybe my brain isnt functioning correctly but I dont see anywhere else to set up my oAuth 2.0 credentials.

Can you please put me out of my misery and point me in the right direction, cheers :-)

[Andrew Wansley]

Ouch—sorry about that. This is a bug and should be fixed shortly.

[Theo Neeskens]

Please do fix it. Just posted the same question....

[Nicolas Lauquin]

Same issue. Thank you for fixing it.

[Andrew Wansley]

Hey guys,

We've made some changes to the registration UI—you should now be able to use that redirect_uri by creating a new client_id and selecting the "installed app" type.

https://code.google.com/apis/console#access

Let me know if you've got any questions.

Andrew

[Andrew Wansley]

Glad to hear it worked for you. On delete: we'll get there, but we wanted to get some of our new features in the hands of our developers as quickly as possible.

On Thu, Apr 21, 2011 at 4:32 PM, Johannes Athmer <joha...@athmer.name> wrote:

Hi,

2011/4/22 Andrew Wansley <aw...@google.com>:

> We've made some changes to the registration UI—you should now be able to use
> that redirect_uri by creating a new client_id and selecting the "installed
> app" type.
> https://code.google.com/apis/console#access

I noticed that change earlier (http://goo.gl/p6ESH) and it looks good
to me. Thanks!

> Let me know if you've got any questions.

Actually, yes:
Why is there no option to delete a Client ID completely? I see that I
can reset the client secret just fine. However, my old Client ID
(which was translated to a web application id) is still shown there.
Is that intentional or did you just want to get the initial change out
soon?

-Johannes

[Nicolas Lauquin]

It's working fine. Thank you !

On 22 avr, 04:11, Andrew Wansley <aw...@google.com> wrote:
> Glad to hear it worked for you. On delete: we'll get there, but we wanted to
> get some of our new features in the hands of our developers as quickly as
> possible.
>

[Rohit Sharma]

As per the above discussion we can have urn:ietf:wg:oauth:2.0:oob in redirect uri for new  client_id. Is there's any fix/procedure available to add urn:ietf:wg:oauth:2.0:oob

 to redirect uri for existing client_id ?

Rohit.