Very nice, thanks! I just spent 2 days trying to do things the other way around.
Is your component IsUserInRole working fine?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3988015#3988015
Reply to the post :
anonymous wrote :
| 2.) I tried using a custom principal class (UserInformation implements
Principal) by specifying the principalClass option for my login module and it
was used throughout the login process. however in my web app I always got a
SimplePrincipal object, when doing
|
You
Thanks for additional information so far... I have two questions - one specific
to the current implementation, one more general. Due to the length of the error
stack trace, I'll post the second question as a second reply to this thread.
First the specific one. I have successfully deployed the
Oh, and I think my security constraints are significantly simple enough that
just the basic @Secure(roles = ...) annotations and the ACL stuff that is in
the exampe seam-security will do all that I need, at least for now. :-)
View the original post :
Hey Shane,
I have one more question regarding the security layer you are currently
building:
As far as i can see you are concentrating on the backend part (calls on
Beanmethods).
What are your plans regarding frontend security (access to web pages / URLs)?
I would like to see the possibility
There will be a component of the security API that handles page security,
however it currently has low priority. In terms of what it will provide, most
likely it will be simple role-based restriction to view-tier resources. There
are plans to support X509 authentication, however it is quite a
The security API is still under heavy construction and I've yet to write
documentation for it. The @Secure annotation is used to secure access to a
component or component method by specifying which roles or permissions are
required to be able to invoke it.
Within the security API there are
Hi, dear Seamers!
I have manged to get a Login Module working which takes Users and Passwords
from an EJB3. After that I use a Session bean that takes the user principal of
the Faces Context's external context and authenticates the user with the seam
authenticator.
login-module.xml:
Almost forgot the login page :-)
|
| s:form method=POST action=j_security_check
| h:panelGrid columns=2
|
|
| f:facet name=header
|
Hi Shane,
Thnx for replying.The example is working only with Seam from CVS, right
? I am working on a project with Seam 1.0.1.GA and wud have loved to get this
working with it. Can you confirm plz ??
Best Regards,
Yogesh,
M-ITC LTD
www.m-itc.net
View the original post :
I'm not sure what's causing the exception, but seam-security.xml is currently
not being used so no need to include it for the time being. That may change
once page security is implemented, but for now the only configuration is in
components.xml.
I'll be working on getting this stuff
11 matches
Mail list logo
