You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by ji...@apache.org on 2004/06/04 02:24:53 UTC
[jira] Commented: (JS2-64) User Attributes - J2 Extension
The following comment has been added to this issue:
Author: David Sean Taylor
Created: Thu, 3 Jun 2004 5:23 PM
Body:
In general I think its a best practice for portlet application portability to use the P3P user profile attributes defined in Appendix D of the Portlet specification. However I could see a need for this in some situations. Im +1 on it, if you think its important enough to prioritize now.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS2-64?page=comments#action_35899
---------------------------------------------------------------------
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: Thu, 3 Jun 2004 5:23 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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org