You'll be able to extend SecurityConfiguration to load roles/permissions from a
database if you like, however keep in mind that these are only explicitly
assigned permissions, as opposed to the dynamic rule-based permissions that the
security API will also support.
As for enums, the type
I just took a look at Seam in the CVS and after going through the seamspace
example I can't say anything else than:
I love you guys! :-)
I've been putting off this project for a long time in lack of a good security
implementation and now you've solved a lot of my problems.
I know you've
How about implementing synchronizer token in seam?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994939#3994939
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994939
___
anonymous wrote : How about implementing synchronizer token in seam?
A what?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995024#3995024
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995024
This text is from core j2ee patterns [1]:
Synchronizer Token
This strategy addresses the problem of duplicate form submissions. A
synchronizer token is set in a user's session and included with each form
returned to the client. When that form is submitted, the synchronizer token in
the form
I went through the road map and I must say I'm really excited to what's coming
up :)
Thanks a lot for the hard and good work.
Richard
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986759#3986759
Reply to the post :
Amazing...
My only concern is that the Security Feature Request is not separated in minor
features for individual voting... I'm interested in Seam's JAAS support over
JSF on Facelets (no j_security_check form action) through Login action bean...
any ways... that's a good plan... congrats!!
Note that the security stuff is in heavy flux. Shane and I and the Drools guys
have been having some discussions about what will be the final form of this
stuff and its turning out pretty interesting (a LOT different to the standard
Java EE security). So anyway, thats why it isn't broken down
Re: Seam security stuff.
Is this also up for discussion with the Portal and Jbpm guys, as I remember you
stating a while ago that you would like to see standardisation between the
products?
Thanks
James
View the original post :
Yeah, but that is outside of the current scope of work. At some stage we need a
unified identity model for all projects, but that won't happen in this work.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986990#3986990
Reply to the post :
10 matches
Mail list logo
