Hi Jerome, This is great - thanks so much for following up. You're right - OAuth is pretty important these days, and we should support it natively in Shiro ASAP. When I get some breathing room in the next few weeks, I'll see if I can incorporate your patches into Shiro's trunk (assuming someone else doesn't beat me to it first!).
Best, -- Les Hazlewood CTO, Stormpath | http://stormpath.com <http://www.stormpath.com/> | 888.391.5282 twitter: @lhazlewood | http://twitter.com/lhazlewood blog: http://leshazlewood.com stormpath blog: http://www.stormpath.com/blog<http://www.stormpath.com/blog/index> On Mon, Apr 23, 2012 at 12:19 PM, jleleu <[email protected]> wrote: > Hi, > > Two months ago, I proposed a patch to add OAuth client support to Shiro > (SHIRO-119) by a new module : shiro-oauth. It was based on the ScribeUP > (1.0.0) library I created for handling user profile after OAuth > authentication (https://github.com/leleuj/scribe-up). > > I had an initial feedback from Kalle, I created a web app demo : > https://github.com/leleuj/scribe-up-shiro-demo, gave some answers and > proposed to create a "login resolver" concept (a bit like the entry point > in > Spring security) to manage login urls and avoid creating specific filters > for OAuth support. But I didn't get any new feedback on this idea. At > least, > specific OAuth filters (even if they are inelegant) are not invasive for > the > Shiro core. > > I believe OAuth is a mainstream protocol and supporting OAuth is a > must-have > feature for the Shiro project. I've made enhancements for the version 1.1.0 > of my ScribeUP library. I upgrade the shiro-oauth module to use this new > version. I update the JIRA ticket SHIRO-119 with my new SVN patch and my > updated documentation. > > I hope that the Shiro community get more interest in the OAuth client > support I propose. > > Thanks. > Best regards, > Jérôme > > > -- > View this message in context: > http://shiro-developer.582600.n2.nabble.com/Add-OAuth-support-for-Shiro-tp7240738p7493004.html > Sent from the Shiro Developer mailing list archive at Nabble.com. >
