Details
-
Type:
Feature Request
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.0.0.Final
-
Fix Version/s: 3.1.0.Beta1
-
Labels:None
-
Affects:Documentation (Ref Guide, User Guide, etc.)
Description
Seam is now using PicketLink API to handle security, in Seam 2 an event was raised to retrieve the actual user entity, yet Seam 3 is lacking this feature. There is not practical way of retrieving a custom extended User.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
You can now write an event observer that listens for org.jboss.seam.security.management.picketlinkIdentityObjectCreatedEvent, which contains the identity object that was created (available from the getIdentityObject() method).
Show
Shane Bryzak
added a comment - You can now write an event observer that listens for org.jboss.seam.security.management.picketlinkIdentityObjectCreatedEvent, which contains the identity object that was created (available from the getIdentityObject() method).
Shane Bryzak
added a comment - You can now write an event observer that listens for org.jboss.seam.security.management.picketlinkIdentityObjectCreatedEvent, which contains the identity object that was created (available from the getIdentityObject() method). 
May be this should be marked as bug? This feature is the only thing that prevents my team from using Seam security. A better integration between Picketlink User and a custom user entity.