Yes, you are correct; there is a mechanism protecting the calls. Up until now, I had been using the FORM method to authenticate with a login servlet. Once authenticated, this authorization mechanism works properly. I wanted to add and use the Seam Identity to do role-based page-level authorzation, and for conditional rendering in my facelets, while keeping the old authorization mechanism for methods. I though that the JAAS authentication would behave the same way, if I specified a jass-config-name in components.xml. I.e., like the call I see in FormAuthenticator: | ... | principal = context.getRealm().authenticate(username,password); | It doesn't appear that the Identity authenticates the way FormAuthenticator did. I guess this is design intent. Since it doesn't, I though I could make this call myself, in an "authenticate-method", something like: | public class Authenticator { | public boolean authenticate() { | .... | Realm realm = ??? | p = realm.authenticate(identity.getUsername(),identity.getPassword()); | ... | return true; | } | Then, if it was OK, I would populate the identity with the user's roles return true. ....But I can't figure out how the get ahold of the/a "Realm" instance. I see that the FormAuthenticator gets it from the context, which comes from the request. Is this workable, or am I missing something obvious....? I am a bit of a novice with JAAS & have to admit it is a bit confusing at times. A dumpstack for My old FORM method authentication. ( I looked at these sources to see how a successful authentication is/was done. ) | at java.lang.Thread.dumpStack(Thread.java:1158) | at centina.sa.server.security.SecurityManager.completeLogin(SecurityManager.java:507) | at centina.sa.server.security.SecurityManagerLoginModule.commit(SecurityManagerLoginModule.java:181) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) | at javax.security.auth.login.LoginContext.login(LoginContext.java:580) Above called at (579) | at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601) | at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344) | at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491) | at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:257) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:416) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:595) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024561#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...