Hi, buji-oauth is too old and has been replaced by buji-pac4j which handles Facebook login (among other protocols and identity providers).
The documentation: https://github.com/bujiio/buji-pac4j should provide you most details. As well as the demo: https://github.com/pac4j/buji-pac4j-demo Thanks. Best regards, Jérôme 2015-12-01 1:34 GMT+01:00 Stephen Beitzel [via Shiro User] < [email protected]>: > I'm writing a service that would like to allow people options for creating > an account and authenticating. A potential user may choose to: > * create an account specific to the service, with a service-specific set > of credentials > * create an account but authenticate via a third party platform (initially > Facebook, but let's allow for Twitter and Google as well) > > The first case is easy enough; I've extended > org.apache.shiro.realm.jdbc.JdbcRealm and have got that working. We > authenticate against a database and we create credentials for new users. > > The second case seems like it would be solvable by using buji-oauth and > setting up a org.pac4j.oauth.client.FacebookClient. However, I'm having > difficulties at the last step (got the oauth token back from Facebook, now > let's login) but the specific error suggests that I'm Doing It Wrong -- I > based my configuration on the demo but deep in the Shiro framework > something is bitching about a missing name. Anyway, there seems to be at > least one and probably several missing steps in the oauth demo and I'm not > at all sure I understand how to proceed. Would someone care to engage with > me to figure out how to get this to work? > > And finally, this leads to another issue: when a service client comes back > to the service at some later time (let's assume that the session has > expired from the session cache) and it wants to access a protected > resource, what knowledge needs to be persisted on the client in order to > reestablish an authenticated session? From my reading of the Shiro > documentation, it appears that I can restrict access to a resource based on > a role criterion (e.g. "CUSTOMER") but I don't see a way to specify a set > of possible authentication methods (e.g. let the user try to login using > any of {Facebook|Basic Auth}). Am I misunderstanding this? > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://shiro-user.582556.n2.nabble.com/Authentication-multiple-realms-and-buji-oauth-tp7580876.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=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.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/Authentication-multiple-realms-and-buji-oauth-tp7580876p7580877.html Sent from the Shiro User mailing list archive at Nabble.com.
