Yeah, I see this buji project and am curious about the intention there as well. I can see the argument for not including oauth client support in shiro, but I don't see the same thing being applicable with CAS. I'll have a look at your patch today, just been a bit busy this summer.
-Jared On Jul 20, 2012 2:10 AM, "jleleu" <[email protected]> wrote: > Hi Jared, > > You should ask Les about this. He's leading Shiro, I'm just trying to > help... > > During six months, I proposed to add OAuth client support to Shiro without > success. Then, thanks to Jason, we created buji-oauth as a Shiro extension > : > https://github.com/bujiio/buji-oauth. > > If you look at bujiio : https://github.com/bujiio, you will find many > other > extensions : buji-cas, buji-guice, buji-openid... with the same source code > (except pom.xml) as you can find on SVN. > > So that's why I think CAS support could be removed from Shiro core and put > into buji-cas extension, to ease lifecycle, additions of new features > (github vs SVN)... > > And as this buji-cas extension is not finished, I'm just trying / proposing > to help on this : I feel concerned because I proposed this CAS support and > I > am a CAS commiter. > > Best regards, > Jérôme > > > > > -- > View this message in context: > http://shiro-developer.582600.n2.nabble.com/Complete-CAS-remember-me-support-tp7577498p7577548.html > Sent from the Shiro Developer mailing list archive at Nabble.com. >
