Grails › Grails - user

OAuth and Grails

Classic

List

Threaded

20 messages Options

pledbrook

OAuth and Grails

Hi,

What do people use for client and server OAuth? It would be great if
there was one go-to plugin for using OAuth and one for being an OAuth
provider, but it's not clear what the best options are.

Thanks,

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

David

Re: OAuth and Grails

+1

Skickat från min iPad

5 apr 2012 kl. 13:49 skrev Peter Ledbrook <[hidden email]>:

> Hi,
>
> What do people use for client and server OAuth? It would be great if
> there was one go-to plugin for using OAuth and one for being an OAuth
> provider, but it's not clear what the best options are.
>
> Thanks,
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Sebastien ARBOGAST

Re: OAuth and Grails

+1

---
Sébastien Arbogast
http://sebastien-arbogast.com

2012/4/5 David Tiselius <[hidden email]>:

> +1
>
> Skickat från min iPad
>
> 5 apr 2012 kl. 13:49 skrev Peter Ledbrook <[hidden email]>:
>
>> Hi,
>>
>> What do people use for client and server OAuth? It would be great if
>> there was one go-to plugin for using OAuth and one for being an OAuth
>> provider, but it's not clear what the best options are.
>>
>> Thanks,
>>
>> Peter
>>
>> --
>> Peter Ledbrook
>> Grails Advocate
>> SpringSource - A Division of VMware
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

smaldini

Re: OAuth and Grails

+100

On Thu, Apr 5, 2012 at 2:57 PM, Sebastien ARBOGAST <[hidden email]> wrote:

+1

---
Sébastien Arbogast
http://sebastien-arbogast.com

2012/4/5 David Tiselius <[hidden email]>:

> +1
>
> Skickat från min iPad
>
> 5 apr 2012 kl. 13:49 skrev Peter Ledbrook <[hidden email]>:
>
>> Hi,
>>
>> What do people use for client and server OAuth? It would be great if
>> there was one go-to plugin for using OAuth and one for being an OAuth
>> provider, but it's not clear what the best options are.
>>
>> Thanks,
>>
>> Peter
>>
>> --
>> Peter Ledbrook
>> Grails Advocate
>> SpringSource - A Division of VMware
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Stéphane MALDINI

bksaville

Re: OAuth and Grails

Not sure about the client side, but the Spring Security OAuth2 provider plugin does work for most cases I believe. And if it doesn't, submit an issue :)

Thanks,

Brian

antony

Re: OAuth and Grails

Hi Peter,

I assume from the pull requests that you've found my oauth-scribe
plugin for the client side. It was designed to replace the oauth
plugin as that uses libraries which haven't been maintained for 4
years.

It has a number of users now and as far as I'm aware it's working for
them. Did you have any success with it?

Cheers,
Antony

On 5 April 2012 14:49, Brian Saville <[hidden email]> wrote:
> Not sure about the client side, but the Spring Security OAuth2 provider
> plugin does work for most cases I believe. And if it doesn't, submit an
> issue :)
>
> Thanks,
> Brian
>

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

pledbrook

Re: OAuth and Grails

> I assume from the pull requests that you've found my oauth-scribe
> plugin for the client side. It was designed to replace the oauth
> plugin as that uses libraries which haven't been maintained for 4
> years.
>
> It has a number of users now and as far as I'm aware it's working for
> them. Did you have any success with it?

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
need to deprecate the other one. In fact, I'd prefer to see this one
become the oauth plugin. Perhaps it could be the oauth 1.0 (and
deprecate oauth-scribe).

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Antony Jones

Re: OAuth and Grails

> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
> need to deprecate the other one. In fact, I'd prefer to see this one
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
> deprecate oauth-scribe).

We (Anthony and I) had discussed that, but felt it might be confusing
to existing oauth plugin users.
However, this would be my preferred solution, as the -scribe prefix
only exists because 'oauth' was taken by its predecessor.
I'll see how long it takes to support multiple providers and meanwhile
see if I can get an official deprecation announcement to the list from
Anthony Campbell.

Cheers,
Antony

On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:

>> I assume from the pull requests that you've found my oauth-scribe
>> plugin for the client side. It was designed to replace the oauth
>> plugin as that uses libraries which haven't been maintained for 4
>> years.
>>
>> It has a number of users now and as far as I'm aware it's working for
>> them. Did you have any success with it?
>
> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
> need to deprecate the other one. In fact, I'd prefer to see this one
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
> deprecate oauth-scribe).
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

acampbell3000

Re: OAuth and Grails

From a usability perspective I guess replacing the new scribe plug-in with the original oauth plug-in would make sense.

Antony would you mind doing that?

Anthony

On 12 Apr 2012, at 18:11, Antony Jones wrote:

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
need to deprecate the other one. In fact, I'd prefer to see this one
become the oauth plugin. Perhaps it could be the oauth 1.0 (and
deprecate oauth-scribe).

We (Anthony and I) had discussed that, but felt it might be confusing
to existing oauth plugin users.
However, this would be my preferred solution, as the -scribe prefix
only exists because 'oauth' was taken by its predecessor.
I'll see how long it takes to support multiple providers and meanwhile
see if I can get an official deprecation announcement to the list from
Anthony Campbell.

Cheers,
Antony

On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
I assume from the pull requests that you've found my oauth-scribe
plugin for the client side. It was designed to replace the oauth
plugin as that uses libraries which haven't been maintained for 4
years.

It has a number of users now and as far as I'm aware it's working for
them. Did you have any success with it?

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
need to deprecate the other one. In fact, I'd prefer to see this one
become the oauth plugin. Perhaps it could be the oauth 1.0 (and
deprecate oauth-scribe).

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Antony Jones

Re: OAuth and Grails

> From a usability perspective I guess replacing the new scribe plug-in with
> the original oauth plug-in would make sense.

Is this the wrong way round? Or do you mean swap the plugins over? I'd
be hasty to add the name -scribe to a plugin which doesn't use scribe
- but perhaps we could call the old oauth plugin 'oauth-signpost' thus
freeing up the 'oauth' name for what is currently 'oauth-scribe'?

I don't mind doing it at all. I can put an announcement up on the
plugin page to explain the situation to existing users of the oauth
plugin.

Cheers,
Antony

On 12 April 2012 19:02, Anthony Campbell <[hidden email]> wrote:

> From a usability perspective I guess replacing the new scribe plug-in with
> the original oauth plug-in would make sense.
>
> Antony would you mind doing that?
>
> Anthony
>
> On 12 Apr 2012, at 18:11, Antony Jones wrote:
>
> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>
> need to deprecate the other one. In fact, I'd prefer to see this one
>
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>
> deprecate oauth-scribe).
>
>
> We (Anthony and I) had discussed that, but felt it might be confusing
> to existing oauth plugin users.
> However, this would be my preferred solution, as the -scribe prefix
> only exists because 'oauth' was taken by its predecessor.
> I'll see how long it takes to support multiple providers and meanwhile
> see if I can get an official deprecation announcement to the list from
> Anthony Campbell.
>
> Cheers,
> Antony
>
> On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
>
> I assume from the pull requests that you've found my oauth-scribe
>
> plugin for the client side. It was designed to replace the oauth
>
> plugin as that uses libraries which haven't been maintained for 4
>
> years.
>
>
> It has a number of users now and as far as I'm aware it's working for
>
> them. Did you have any success with it?
>
>
> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>
> need to deprecate the other one. In fact, I'd prefer to see this one
>
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>
> deprecate oauth-scribe).
>
>
> Peter
>
>
> --
>
> Peter Ledbrook
>
> Grails Advocate
>
> SpringSource - A Division of VMware
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe from this list, please visit:
>
>
> http://xircles.codehaus.org/manage_email
>
>
>
>
>
>
> --
> ________________________________
> ꜽ . antony jones . http://www.enzy.org
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

acampbell3000

Re: OAuth and Grails

In reply to this post by Antony Jones

No swap. Effectively deprecate your plug-in and move release your latest build and the next version of oauth.

I'm just thinking in terms of someone new to Grails and looking for a oauth plug-in. Makes sense to try "oauth" etc.

Anthony

On 12 Apr 2012, at 18:11, Antony Jones wrote:

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
need to deprecate the other one. In fact, I'd prefer to see this one
become the oauth plugin. Perhaps it could be the oauth 1.0 (and
deprecate oauth-scribe).

We (Anthony and I) had discussed that, but felt it might be confusing
to existing oauth plugin users.
However, this would be my preferred solution, as the -scribe prefix
only exists because 'oauth' was taken by its predecessor.
I'll see how long it takes to support multiple providers and meanwhile
see if I can get an official deprecation announcement to the list from
Anthony Campbell.

Cheers,
Antony

On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
I assume from the pull requests that you've found my oauth-scribe
plugin for the client side. It was designed to replace the oauth
plugin as that uses libraries which haven't been maintained for 4
years.

It has a number of users now and as far as I'm aware it's working for
them. Did you have any success with it?

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
need to deprecate the other one. In fact, I'd prefer to see this one
become the oauth plugin. Perhaps it could be the oauth 1.0 (and
deprecate oauth-scribe).

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Antony Jones

Re: OAuth and Grails

Ah, yes - ok so that I think was peter's suggestion too.
I'm happy to do this - I'll get on with it!

Cheers,
Antony

On 12 April 2012 19:10, Anthony Campbell <[hidden email]> wrote:

> No swap. Effectively deprecate your plug-in and move release your latest
> build and the next version of oauth.
>
> I'm just thinking in terms of someone new to Grails and looking for a oauth
> plug-in. Makes sense to try "oauth" etc.
>
> Anthony
>
> On 12 Apr 2012, at 18:11, Antony Jones wrote:
>
> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>
> need to deprecate the other one. In fact, I'd prefer to see this one
>
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>
> deprecate oauth-scribe).
>
>
> We (Anthony and I) had discussed that, but felt it might be confusing
> to existing oauth plugin users.
> However, this would be my preferred solution, as the -scribe prefix
> only exists because 'oauth' was taken by its predecessor.
> I'll see how long it takes to support multiple providers and meanwhile
> see if I can get an official deprecation announcement to the list from
> Anthony Campbell.
>
> Cheers,
> Antony
>
> On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
>
> I assume from the pull requests that you've found my oauth-scribe
>
> plugin for the client side. It was designed to replace the oauth
>
> plugin as that uses libraries which haven't been maintained for 4
>
> years.
>
>
> It has a number of users now and as far as I'm aware it's working for
>
> them. Did you have any success with it?
>
>
> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>
> need to deprecate the other one. In fact, I'd prefer to see this one
>
> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>
> deprecate oauth-scribe).
>
>
> Peter
>
>
> --
>
> Peter Ledbrook
>
> Grails Advocate
>
> SpringSource - A Division of VMware
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe from this list, please visit:
>
>
> http://xircles.codehaus.org/manage_email
>
>
>
>
>
>
> --
> ________________________________
> ꜽ . antony jones . http://www.enzy.org
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

acampbell3000

Re: OAuth and Grails

Antony,

Forgot to check - in going to deprecate the source on GitHub. Can you confirm your project for me?

Anthony

On 12 Apr 2012, at 19:36, Antony Jones <[hidden email]> wrote:

> Ah, yes - ok so that I think was peter's suggestion too.
> I'm happy to do this - I'll get on with it!
>
> Cheers,
> Antony
>
> On 12 April 2012 19:10, Anthony Campbell <[hidden email]> wrote:
>> No swap. Effectively deprecate your plug-in and move release your latest
>> build and the next version of oauth.
>>
>> I'm just thinking in terms of someone new to Grails and looking for a oauth
>> plug-in. Makes sense to try "oauth" etc.
>>
>> Anthony
>>
>> On 12 Apr 2012, at 18:11, Antony Jones wrote:
>>
>> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>>
>> need to deprecate the other one. In fact, I'd prefer to see this one
>>
>> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>>
>> deprecate oauth-scribe).
>>
>>
>> We (Anthony and I) had discussed that, but felt it might be confusing
>> to existing oauth plugin users.
>> However, this would be my preferred solution, as the -scribe prefix
>> only exists because 'oauth' was taken by its predecessor.
>> I'll see how long it takes to support multiple providers and meanwhile
>> see if I can get an official deprecation announcement to the list from
>> Anthony Campbell.
>>
>> Cheers,
>> Antony
>>
>> On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
>>
>> I assume from the pull requests that you've found my oauth-scribe
>>
>> plugin for the client side. It was designed to replace the oauth
>>
>> plugin as that uses libraries which haven't been maintained for 4
>>
>> years.
>>
>>
>> It has a number of users now and as far as I'm aware it's working for
>>
>> them. Did you have any success with it?
>>
>>
>> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>>
>> need to deprecate the other one. In fact, I'd prefer to see this one
>>
>> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>>
>> deprecate oauth-scribe).
>>
>>
>> Peter
>>
>>
>> --
>>
>> Peter Ledbrook
>>
>> Grails Advocate
>>
>> SpringSource - A Division of VMware
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe from this list, please visit:
>>
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>>
>>
>> --
>> ________________________________
>> ꜽ . antony jones . http://www.enzy.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
>
> --
> ________________________________
> ꜽ . antony jones . http://www.enzy.org
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Antony Jones

Re: OAuth and Grails

Hi Anthony,

How do you mean confirm it?
I'm currently making changes to the plugin to support multiple
providers - all going well I don't see it taking more than another
day, it's almost there. When that is done I'll release it as 'oauth'.

If you mean confirm as in the plan is definite - yep - as soon as I
have the multi-provider work done I'll release it.

Cheers,
Antony

On 16 April 2012 00:53, Anthony Campbell <[hidden email]> wrote:

> Antony,
>
> Forgot to check - in going to deprecate the source on GitHub. Can you confirm your project for me?
>
> Anthony
>
> On 12 Apr 2012, at 19:36, Antony Jones <[hidden email]> wrote:
>
>> Ah, yes - ok so that I think was peter's suggestion too.
>> I'm happy to do this - I'll get on with it!
>>
>> Cheers,
>> Antony
>>
>> On 12 April 2012 19:10, Anthony Campbell <[hidden email]> wrote:
>>> No swap. Effectively deprecate your plug-in and move release your latest
>>> build and the next version of oauth.
>>>
>>> I'm just thinking in terms of someone new to Grails and looking for a oauth
>>> plug-in. Makes sense to try "oauth" etc.
>>>
>>> Anthony
>>>
>>> On 12 Apr 2012, at 18:11, Antony Jones wrote:
>>>
>>> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>>>
>>> need to deprecate the other one. In fact, I'd prefer to see this one
>>>
>>> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>>>
>>> deprecate oauth-scribe).
>>>
>>>
>>> We (Anthony and I) had discussed that, but felt it might be confusing
>>> to existing oauth plugin users.
>>> However, this would be my preferred solution, as the -scribe prefix
>>> only exists because 'oauth' was taken by its predecessor.
>>> I'll see how long it takes to support multiple providers and meanwhile
>>> see if I can get an official deprecation announcement to the list from
>>> Anthony Campbell.
>>>
>>> Cheers,
>>> Antony
>>>
>>> On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:
>>>
>>> I assume from the pull requests that you've found my oauth-scribe
>>>
>>> plugin for the client side. It was designed to replace the oauth
>>>
>>> plugin as that uses libraries which haven't been maintained for 4
>>>
>>> years.
>>>
>>>
>>> It has a number of users now and as far as I'm aware it's working for
>>>
>>> them. Did you have any success with it?
>>>
>>>
>>> Yes. As I mentioned in direct chat, if this supersedes oauth plugin we
>>>
>>> need to deprecate the other one. In fact, I'd prefer to see this one
>>>
>>> become the oauth plugin. Perhaps it could be the oauth 1.0 (and
>>>
>>> deprecate oauth-scribe).
>>>
>>>
>>> Peter
>>>
>>>
>>> --
>>>
>>> Peter Ledbrook
>>>
>>> Grails Advocate
>>>
>>> SpringSource - A Division of VMware
>>>
>>>
>>> ---------------------------------------------------------------------
>>>
>>> To unsubscribe from this list, please visit:
>>>
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> ________________________________
>>> ꜽ . antony jones . http://www.enzy.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>>
>>
>> --
>> ________________________________
>> ꜽ . antony jones . http://www.enzy.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

acampbell3000

Re: OAuth and Grails

Wow,

It was late when I wrote to you though. I meant - confirm the source of your plug-in. I still need to add a README of some sort redirecting from my source to your source!

Anthony

On 16 Apr 2012, at 10:03, Antony Jones wrote:

Hi Anthony,

How do you mean confirm it?
I'm currently making changes to the plugin to support multiple
providers - all going well I don't see it taking more than another
day, it's almost there. When that is done I'll release it as 'oauth'.

If you mean confirm as in the plan is definite - yep - as soon as I
have the multi-provider work done I'll release it.

Cheers,
Antony

On 16 April 2012 00:53, Anthony Campbell <[hidden email]> wrote:
Antony,

Forgot to check - in going to deprecate the source on GitHub. Can you confirm your project for me?

Anthony

On 12 Apr 2012, at 19:36, Antony Jones <[hidden email]> wrote:

Ah, yes - ok so that I think was peter's suggestion too.
I'm happy to do this - I'll get on with it!

Cheers,
Antony

On 12 April 2012 19:10, Anthony Campbell <[hidden email]> wrote:
No swap. Effectively deprecate your plug-in and move release your latest
build and the next version of oauth.

I'm just thinking in terms of someone new to Grails and looking for a oauth
plug-in. Makes sense to try "oauth" etc.

Anthony

On 12 Apr 2012, at 18:11, Antony Jones wrote:

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we

need to deprecate the other one. In fact, I'd prefer to see this one

become the oauth plugin. Perhaps it could be the oauth 1.0 (and

deprecate oauth-scribe).

We (Anthony and I) had discussed that, but felt it might be confusing
to existing oauth plugin users.
However, this would be my preferred solution, as the -scribe prefix
only exists because 'oauth' was taken by its predecessor.
I'll see how long it takes to support multiple providers and meanwhile
see if I can get an official deprecation announcement to the list from
Anthony Campbell.

Cheers,
Antony

On 12 April 2012 16:05, Peter Ledbrook <[hidden email]> wrote:

I assume from the pull requests that you've found my oauth-scribe

plugin for the client side. It was designed to replace the oauth

plugin as that uses libraries which haven't been maintained for 4

years.

It has a number of users now and as far as I'm aware it's working for

them. Did you have any success with it?

Yes. As I mentioned in direct chat, if this supersedes oauth plugin we

need to deprecate the other one. In fact, I'd prefer to see this one

become the oauth plugin. Perhaps it could be the oauth 1.0 (and

deprecate oauth-scribe).

Peter

--

Peter Ledbrook

Grails Advocate

SpringSource - A Division of VMware

---------------------------------------------------------------------

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
________________________________
ꜽ . antony jones . http://www.enzy.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Marc Palmer Local

Re: OAuth and Grails

This is great news guys.

How about updating http://grails.org/plugin/oauth with info on what services this is known to work with, and recipes for auth'ing with various big-name services?

Marc

~ ~ ~
Marc Palmer
Freelancer (Grails/Groovy/Java/UX)

I offer commercial support for Grails plugins from as low as $50/mo.
For details see: http://grailsrocks.com

Blog: http://www.anyware.co.uk | Resumé: http://www.anyware.co.uk/marc
Contributor @ http://grails.org | Founder @ http://noticelocal.com
Developer @ http://weceem.org | Member @ http://spottymushroom.com
Twitter: http://twitter.com/wangjammer5

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Vineel

Re: OAuth and Grails

In reply to this post by pledbrook

does the oauth-scribe plugin work as a provider as well?

Antony Jones

Re: OAuth and Grails

vineen: No, it is the consumer only.

Marc: As soon as I release I'll provide information about what it
works with (technically, it should be anything which oauth-scribe
supports so maybe I'll link to their list)

Anthony: Yep I'll link to the source, likely from the docs which I'll
change to grails docs format. I'm very close to releasing now, the
multi-provider work just needs a little further testing before I
commit.

Cheers,
Antony

On 16 April 2012 14:41, vineeln <[hidden email]> wrote:

> does the oauth-scribe plugin work as a provider as well?
>
> --
> View this message in context: http://grails.1312388.n4.nabble.com/OAuth-and-Grails-tp4534616p4561559.html
> Sent from the Grails - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

Vineel

Re: OAuth and Grails

Thanks Antony!

this may be too early to ask, but are there plans to add provider support to this plugin in future? or do you guys know of any plugin that has the OAuth provider functionality.

Thanks
-Vineel

David

Re: OAuth and Grails

http://grails.org/plugin/spring-security-oauth2-provider

/David
- on the phone

Den 17 apr 2012 05:38 skrev "vineeln" <[hidden email]>:

Thanks Antony!

this may be too early to ask, but are there plans to add provider support to
this plugin in future? or do you guys know of any plugin that has the OAuth
provider functionality.

Thanks
-Vineel

--
View this message in context: http://grails.1312388.n4.nabble.com/OAuth-and-Grails-tp4534616p4563470.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email