Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/JS2-64 Here is an overview of the issue: --------------------------------------------------------------------- Key: JS2-64 Summary: User Attributes - J2 Extension Type: New Feature Status: Open Priority: Major Project: Jetspeed 2 Fix Fors: 2.0-dev/cvs Versions: 2.0-dev/cvs Assignee: David Le Strat Reporter: David Le Strat Created: Wed, 2 Jun 2004 6:28 PM Updated: Wed, 2 Jun 2004 6:28 PM Description: In the current portlet specs, there is no capability for mapping ref to link for user attributes between a portlet and the portal implementation. In a portlet application, we can specify which user attribute the portlet will use. For instance: <user-attribute> <description>User Given Name</description> <name>user.name.given</name> </user-attribute> where user.name.given is the name of the attribute in the portal and the portlet. But what if, we want to deploy prebuilt portlets in J2 which leverage user attribute but the portlet code user is user-name-given instead of user.name.given used by the portal. It therefore seems to me, that the same way security mapping has a role-name and a role-link, the same should apply to user attribute. I am proposing that we leverage jetspeed-portlet.xml to support such a mapping. If no mapping is specified then the default behavior takes place, if a mapping is specified in jetspeed-portlet.xml, J2 will leverage that mapping as a way to map J2 user attributes to the portlet user attribute (in the example above, user-name-given to user.name.given). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
