[
http://jira.jboss.com/jira/browse/JBPORTAL-1043?page=all ]
Boleslaw Dawidowicz resolved JBPORTAL-1043.
-------------------------------------------
Resolution: Done
Ready in SVN. This need to be documented. Not all information present in config files is
used currently. Implementation should be extended for beta
introduce UserProfile and user metadata (storage mechanism agnostic)
--------------------------------------------------------------------
Key: JBPORTAL-1043
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1043
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.Alpha1
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.Alpha1
- Each user entry (ldap or database table) can bring different set of user personal
information. This makes the user profile
- In portal we have property names like: user.name, user.surname, user.email, user.phone
and etc.
- Each UserModule implementation provide a mapping of properties to coresponding values
in underlaying database or directory
(table columns or ldat entry attributes for eg.)
- Profile informations are accessed using API like:
user.getMetaData().getProfileMetaData().getProperty(User.NAME_PROPERTY);
.getAllProperties().iterator()
- Currently this is handled by PropertyMap - keept as separate table in DB
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira