This content has been marked as final.
Show 3 replies
-
1. Re: Problems with Seam Security
shane.bryzak Feb 6, 2007 11:41 AM (in response to m.schuetz)Seam security only uses JAAS for authentication, and does not integrate with container security at this point in time. I'm guessing you are using the @RolesAllowed annotation on your bean? If so, you need to replace it with @Restrict (a Seam annotation) - see the docs for usage.
-
2. Re: Problems with Seam Security
stony Feb 7, 2007 5:52 AM (in response to m.schuetz)Is it planned to integrate seam with container security in future ? What about the jaasConfigName attribute ?
<security:identity authenticate-method="#{myAuthenticator.authenticate}" jaasConfigName="myDomain" />
After deploying this (using the last nightly build 06-02-07) and using the Identity object for authentification, the container didn't recognize the new principal anyway. -
3. Re: Problems with Seam Security
shane.bryzak Feb 7, 2007 7:56 AM (in response to m.schuetz)It is planned for a future release. Setting the jaasConfigName property will allow Seam to authenticate using a different jaas configuration (other than the built-in one), it won't allow the container to authenticate using Seam security.