Jérôme I probably wasn't very clear in my last mail. Not yet enough coffee in the system.
A problem I saw with your demo, which offhand I couldn't see a way round, (and of course I may be wrong) is that IF a user tries to access a protected page when not authorised, THEN I want a page to pop up which lets her choose the provider. My demo does this with a standard login page. Yours seemed to jump to whichever provider was protecting that page. Again, I may well have got it wrong, but it was a decision made in good faith at the time. Tim On 11 October 2012 09:56, jleleu [via Shiro User] < [email protected]> wrote: > Hi Tim, > > I prefer to keep public answers which can help others. > > About you Maven issues, it's really strange : the sonatype snapshots > repository is defined in the parent pom (oss-parent) and the dependencies > you added are already defined in scribe-up project. > > For Google, you're right, you have to define the end-point, but you can do > that in buji-oauth by using the Google2Provider and setting its scope to : > EMAIL (PROFILE and EMAIL_AND_PROFILE are also possible). > > I'm in line with having a common profile to ease work with multiple > providers. To check and add users into database, it's somehow really > specific to your environement. But, you can customize the Realm as usually > for Shiro projects. In this case, it's the OAuthRealm on which you can > override the doGetAuthenticationInfo or doGetAuthorizationInfo methods > according to your needs. > > About nonce, I integrated a pull request to add the use of the state > parameter in Facebook case. > > About showing you how to duplicate current functionnaly with less code, > it's exactly the objective of the demo : > https://github.com/leleuj/scribe-up-shiro-demo. Showing to everybody how > to use buji-oauth. > Less code is easy as you re-develop most of what is already in buji-oauth, > but more configuration is also required. > I'll send you a private email for this. > > In buji-oauth, you already have the following providers : Facebook, Google > (OAuth 1.0 & 2.0), Twitter, DropBox, LinkedIn, Yahoo, Windows Live, > WordPress and GitHub with very complete profiles (just not only the email). > It's too bad not to leverage your work on this. > > Best regards, > Jérôme > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://shiro-user.582556.n2.nabble.com/OAuth-demo-tp7577850p7577858.html > To start a new topic under Shiro User, email > [email protected] > To unsubscribe from Shiro User, click > here<http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=582556&code=dGltLm5pYmxldHRAY2lsb2dpLmNvbXw1ODI1NTZ8MTMwMDYyMTY=> > . > 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.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-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/OAuth-demo-tp7577850p7577861.html Sent from the Shiro User mailing list archive at Nabble.com.
