Hi Marinus, For your current situation, the fastest option would be the second one you listed - create a quick JAAS LoginModule that delegates to Shiro. Another approach is to have Shiro delegate to the JAAS LoginModule - whichever is fastest for you.
HTH, Les On Mon, Nov 21, 2011 at 2:04 AM, geuze <[email protected]> wrote: > Dear Shiro users, > > I have a problem with getting SSO to work on a JBoss EAP 5.1.1 server. > > My JBoss server is configured for SSO by setting this value in the > server.xml configuration file: > > <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> > > This worked fine when we worked with JAAS. However we’ve switched to Shiro > and now SSO does not work anymore. This seems logical because these > limitations are stated by this website > http://community.jboss.org/wiki/JBossWebSingleSignOn concerning the > SingleSignOn implementation: “Requires use of container managed > authentication (via <login-config> element in web.xml)” > > However we use Shiro now, so we have no login-config anymore in our web.xml. > > My question is: has anyone some suggestions how to solve this problem? > - Should I use Shiro native session management? If so, what is the best way > to do this? > - Should I make an own JAAS Login module which delegates the login logic to > Shiro (and by that reactive my container managed authentication in the > web.xml again?) > > I hope someone can provide me some help. > > Thanks in advance. > > Greets, > Marinus > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/SSO-with-Shiro-on-JBoss-EAP-5-1-1-tp7015850p7015850.html > Sent from the Shiro User mailing list archive at Nabble.com.
