You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@shiro.apache.org by jleleu <le...@gmail.com> on 2012/07/25 19:10:21 UTC
Shiro now supports OAuth (client mode)
Hi,
I'm pretty happy to announce that Shiro now supports OAuth (client mode)
with the buji-oauth extension : https://github.com/bujiio/buji-oauth.
It means that you can create an application for Facebook, Twitter... :
authenticate at the OAuth provider and then be authenticated in Shiro
application with a complete user profile.
So far, the following OAuth providers are supported :
- Facebook
- GitHub
- Google
- LinkedIn
- Twitter
- Windows Live
- WordPress
- Yahoo
I'm currently working on DropBox support. If you need support for some other
OAuth provider, just let me know.
Any feedback will be greatly appreciated.
Best regards,
Jérôme
--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637.html
Sent from the Shiro User mailing list archive at Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by Les Hazlewood <lh...@apache.org>.
> Sorry for the vain joy and the "misleading mail". It clearly wasn't my
> objective.
I definitely don't want to squash the joy! I think what you've put
together is great! :)
And I don't think anyone thought you were intentionally doing anything
'misleading' (you weren't). I just wanted to clarify for future
reference: the ASF can get very testy if this stuff isn't defined
properly. I'm personally happy and grateful to have you as such a
helpful member of the Shiro community - I just wanted to let you know
about the ASF rules so we can be careful about this moving forward.
Please keep up the awesome work!
> I didn't know that the expression "Shiro supports X" was so meaningfull.
It can be interpreted in a specific way for ASF projects, so I was
just being careful.
> should work very well. Just give it a try, take a look at the demo...
> Any help or feedback is welcome.
Again, great work - I'm really happy to see this and I hope people like it!
Cheers,
Les
Re: Shiro now supports OAuth (client mode)
Posted by jleleu <le...@gmail.com>.
Hi,
Sorry for the vain joy and the "misleading mail". It clearly wasn't my
objective.
I didn't know that the expression "Shiro supports X" was so meaningfull.
That said, even *unofficial*, this extension has been properly tested and
should work very well. Just give it a try, take a look at the demo...
Any help or feedback is welcome.
Best regards,
Jérôme
--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7577644.html
Sent from the Shiro User mailing list archive at Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by Les Hazlewood <lh...@apache.org>.
Hi Marcus,
Don't worry, OAuth is definitely on the roadmap for an officially
supported extension! Buji could be a source for that extension - it
depends on how the Shiro dev team feels about how we want to
incorporate it.
Buji, while not an official part of Apache Shiro, allows people to
play at their own pace for things that they may need faster than the
Shiro dev team timeline, or for things worth prototyping. I
personally would like to see Buji act as a 'feeder' into Shiro for the
more popular things, for sure (assuming all of the Intellectual
Property and License Agreement mandates required by the ASF work out).
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk
On Wed, Jul 25, 2012 at 11:30 AM, Marcus Bond <ma...@marcusbond.me.uk> wrote:
> Great news, almost. I was looking for OAuth support in Shiro and this is
> undoubtedly a great extension BUT the initial excitement I had in thinking
> that Shiro itself now had inbuilt OAuth support has been tempered by
> realising this is not actually an official Shiro feature.
>
> I like Shiro and also that Les has staked a business on its quality and
> hopefully success however I'm a little disappointed to learn that despite
> the headline OAuth support is actually an unofficial side project (the
> disappointment lies with the misleading mail not the Shiro project btw)..
>
> @Les, with you being involved with this extension is it something that is
> likely to be rolled in with Shiro at a later date or will it likely remain
> separate? Also, I have read differing articles over the last few weeks but
> is Shiro or an extension likely to provide an Oauth service itself in the
> future?
>
> Regards,
> Marcus.
>
> -----Original Message-----
> From: Les Hazlewood [mailto:lhazlewood@apache.org]
> Sent: 25 July 2012 18:43
> To: user@shiro.apache.org
> Subject: Re: Shiro now supports OAuth (client mode)
>
> Hi Jerome,
>
> Thanks for the notice!
>
> I have a small request though: can you please not say "Shiro supports X..."
> on the Shiro community lists? Per Apache Software Foundation rules, we're
> only allowed to say "Apache Shiro supports X" if X is officially supported
> by the Apache Shiro development team.
>
> I think it's great that the (non-official) Buji project is being helpful for
> things like OAuth with Shiro, but people should know that Buji is not an
> officially supported project w.r.t. Apache Shiro. It is for community-led
> and community-supported extensions to the Apache Shiro project, just like
> WicketStuff relates to Apache Wicket.
>
> That being said, I personally love to see how actively you are helping the
> community. Please keep it up!
>
> Best regards,
>
> --
> Les Hazlewood | @lhazlewood
> CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
> Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk
>
> On Wed, Jul 25, 2012 at 10:10 AM, jleleu <le...@gmail.com> wrote:
>> Hi,
>>
>> I'm pretty happy to announce that Shiro now supports OAuth (client
>> mode) with the buji-oauth extension :
> https://github.com/bujiio/buji-oauth.
>> It means that you can create an application for Facebook, Twitter... :
>> authenticate at the OAuth provider and then be authenticated in Shiro
>> application with a complete user profile.
>>
>> So far, the following OAuth providers are supported :
>> - Facebook
>> - GitHub
>> - Google
>> - LinkedIn
>> - Twitter
>> - Windows Live
>> - WordPress
>> - Yahoo
>>
>> I'm currently working on DropBox support. If you need support for some
>> other OAuth provider, just let me know.
>>
>> Any feedback will be greatly appreciated.
>>
>> Best regards,
>> Jérôme
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client
>> -mode-tp7577637.html Sent from the Shiro User mailing list archive at
>> Nabble.com.
>
RE: Shiro now supports OAuth (client mode)
Posted by Marcus Bond <ma...@marcusbond.me.uk>.
Great news, almost. I was looking for OAuth support in Shiro and this is
undoubtedly a great extension BUT the initial excitement I had in thinking
that Shiro itself now had inbuilt OAuth support has been tempered by
realising this is not actually an official Shiro feature.
I like Shiro and also that Les has staked a business on its quality and
hopefully success however I'm a little disappointed to learn that despite
the headline OAuth support is actually an unofficial side project (the
disappointment lies with the misleading mail not the Shiro project btw)..
@Les, with you being involved with this extension is it something that is
likely to be rolled in with Shiro at a later date or will it likely remain
separate? Also, I have read differing articles over the last few weeks but
is Shiro or an extension likely to provide an Oauth service itself in the
future?
Regards,
Marcus.
-----Original Message-----
From: Les Hazlewood [mailto:lhazlewood@apache.org]
Sent: 25 July 2012 18:43
To: user@shiro.apache.org
Subject: Re: Shiro now supports OAuth (client mode)
Hi Jerome,
Thanks for the notice!
I have a small request though: can you please not say "Shiro supports X..."
on the Shiro community lists? Per Apache Software Foundation rules, we're
only allowed to say "Apache Shiro supports X" if X is officially supported
by the Apache Shiro development team.
I think it's great that the (non-official) Buji project is being helpful for
things like OAuth with Shiro, but people should know that Buji is not an
officially supported project w.r.t. Apache Shiro. It is for community-led
and community-supported extensions to the Apache Shiro project, just like
WicketStuff relates to Apache Wicket.
That being said, I personally love to see how actively you are helping the
community. Please keep it up!
Best regards,
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk
On Wed, Jul 25, 2012 at 10:10 AM, jleleu <le...@gmail.com> wrote:
> Hi,
>
> I'm pretty happy to announce that Shiro now supports OAuth (client
> mode) with the buji-oauth extension :
https://github.com/bujiio/buji-oauth.
> It means that you can create an application for Facebook, Twitter... :
> authenticate at the OAuth provider and then be authenticated in Shiro
> application with a complete user profile.
>
> So far, the following OAuth providers are supported :
> - Facebook
> - GitHub
> - Google
> - LinkedIn
> - Twitter
> - Windows Live
> - WordPress
> - Yahoo
>
> I'm currently working on DropBox support. If you need support for some
> other OAuth provider, just let me know.
>
> Any feedback will be greatly appreciated.
>
> Best regards,
> Jérôme
>
>
>
>
> --
> View this message in context:
> http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client
> -mode-tp7577637.html Sent from the Shiro User mailing list archive at
> Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by Les Hazlewood <lh...@apache.org>.
Hi Jerome,
Thanks for the notice!
I have a small request though: can you please not say "Shiro supports
X..." on the Shiro community lists? Per Apache Software Foundation
rules, we're only allowed to say "Apache Shiro supports X" if X is
officially supported by the Apache Shiro development team.
I think it's great that the (non-official) Buji project is being
helpful for things like OAuth with Shiro, but people should know that
Buji is not an officially supported project w.r.t. Apache Shiro. It
is for community-led and community-supported extensions to the Apache
Shiro project, just like WicketStuff relates to Apache Wicket.
That being said, I personally love to see how actively you are helping
the community. Please keep it up!
Best regards,
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk
On Wed, Jul 25, 2012 at 10:10 AM, jleleu <le...@gmail.com> wrote:
> Hi,
>
> I'm pretty happy to announce that Shiro now supports OAuth (client mode)
> with the buji-oauth extension : https://github.com/bujiio/buji-oauth.
> It means that you can create an application for Facebook, Twitter... :
> authenticate at the OAuth provider and then be authenticated in Shiro
> application with a complete user profile.
>
> So far, the following OAuth providers are supported :
> - Facebook
> - GitHub
> - Google
> - LinkedIn
> - Twitter
> - Windows Live
> - WordPress
> - Yahoo
>
> I'm currently working on DropBox support. If you need support for some other
> OAuth provider, just let me know.
>
> Any feedback will be greatly appreciated.
>
> Best regards,
> Jérôme
>
>
>
>
> --
> View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637.html
> Sent from the Shiro User mailing list archive at Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by jleleu <le...@gmail.com>.
Hi,
We have started working on extending pac4j libraries including buji-pac4j.
The idea is to be able to login users not only through the default webflow
with an external identity provider, but also to be able to authenticate REST
requests.
It's almost done for the default J2E implementation of pac4j
(https://github.com/leleuj/j2e-pac4j/commit/e960963ea10c73805ef33b00cb36c86c896f714d).
We are trying to imagine various use cases. For your point number 2, could
you elaborate a little more about it? How does authentication happen? What
are the credentials? Is Twitter a real use case or just an example? etc.
Thanks.
Best regards,
Jérôme
--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580351.html
Sent from the Shiro User mailing list archive at Nabble.com.
RE: Shiro now supports OAuth (client mode)
Posted by Konrad Zuse <th...@hotmail.com>.
Nice nice!!! I would talk to Lez about OAuth in Shiro 2.0. I believe there was mention about it, but I believe that it's good to talk to the boss and see what's going on. I'm excited for Shiro 2.0 when it's ready!
> Date: Tue, 25 Nov 2014 23:48:51 -0700
> From: leleuj@gmail.com
> To: user@shiro.apache.org
> Subject: Re: Shiro now supports OAuth (client mode)
>
> Hi,
>
> The first use case is handled currently by buji-pac4j. You can delegate the
> user authentication to a lot of well-known providers (Facebook, Twitter...)
> This flow requires redirections between the application and the identity
> provider and some UI interaction from the user (to enter his credentials).
>
> The second use case is not implemented yet, but we have some discussions
> about allowing straight authentication (to support REST) and that allows
> this kind of scenario. So it might come sooner than expected.
>
> The home page of the project: https://github.com/bujiio/buji-pac4j should
> provide you enough documentation. Just let me know if you feel that
> something is missing.
>
> Thanks.
> Best regards,
>
> Jérôme LELEU
> Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj
> Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org
>
> 2014-11-25 19:53 GMT+01:00 agilone [via Shiro User] <
> ml-node+s582556n7580339h77@n2.nabble.com>:
>
> > Hi Jérôme,
> >
> > Would you please let me know if implementing following cases are possible
> > with your integrations?
> >
> > 1- Oauth 2.0 with known providers and custom provider
> > 2- Oauth 2.0 app to app type of authentication (using bearer tokens -
> > https://dev.twitter.com/oauth/application-only)
> >
> > also it would be nice if you can explain little bit how we can achieve
> > such integration - we already have Shiro in place for authentication.
> >
> > Thanks
> >
> > ED
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> > http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580339.html
> > To start a new topic under Shiro User, email
> > ml-node+s582556n582556h4@n2.nabble.com
> > To unsubscribe from Shiro User, click here
> > <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=582556&code=bGVsZXVqQGdtYWlsLmNvbXw1ODI1NTZ8LTExNzY2MzcxMTY=>
> > .
> > NAML
> > <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580342.html
> Sent from the Shiro User mailing list archive at Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by jleleu <le...@gmail.com>.
Hi,
The first use case is handled currently by buji-pac4j. You can delegate the
user authentication to a lot of well-known providers (Facebook, Twitter...)
This flow requires redirections between the application and the identity
provider and some UI interaction from the user (to enter his credentials).
The second use case is not implemented yet, but we have some discussions
about allowing straight authentication (to support REST) and that allows
this kind of scenario. So it might come sooner than expected.
The home page of the project: https://github.com/bujiio/buji-pac4j should
provide you enough documentation. Just let me know if you feel that
something is missing.
Thanks.
Best regards,
Jérôme LELEU
Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj
Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org
2014-11-25 19:53 GMT+01:00 agilone [via Shiro User] <
ml-node+s582556n7580339h77@n2.nabble.com>:
> Hi Jérôme,
>
> Would you please let me know if implementing following cases are possible
> with your integrations?
>
> 1- Oauth 2.0 with known providers and custom provider
> 2- Oauth 2.0 app to app type of authentication (using bearer tokens -
> https://dev.twitter.com/oauth/application-only)
>
> also it would be nice if you can explain little bit how we can achieve
> such integration - we already have Shiro in place for authentication.
>
> Thanks
>
> ED
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580339.html
> To start a new topic under Shiro User, email
> ml-node+s582556n582556h4@n2.nabble.com
> To unsubscribe from Shiro User, click here
> <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=582556&code=bGVsZXVqQGdtYWlsLmNvbXw1ODI1NTZ8LTExNzY2MzcxMTY=>
> .
> NAML
> <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580342.html
Sent from the Shiro User mailing list archive at Nabble.com.
Re: Shiro now supports OAuth (client mode)
Posted by agilone <er...@medyanova.com>.
Hi Jérôme,
Would you please let me know if implementing following cases are possible
with your integrations?
1- Oauth 2.0 with known providers and custom provider
2- Oauth 2.0 app to app type of authentication (using bearer tokens -
https://dev.twitter.com/oauth/application-only)
also it would be nice if you can explain little bit how we can achieve such
integration - we already have Shiro in place for authentication.
Thanks
ED
--
View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-now-supports-OAuth-client-mode-tp7577637p7580339.html
Sent from the Shiro User mailing list archive at Nabble.com.