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 "Ate Douma (JIRA)" <je...@portals.apache.org> on 2006/04/28 23:14:37 UTC
[jira] Created: (JS2-527) Allow email addressed to be used for user
accounts by making hierarchical interpretation of principal names optional
Allow email addressed to be used for user accounts by making hierarchical interpretation of principal names optional
----------------------------------------------------------------------------------------------------------------------
Key: JS2-527
URL: http://issues.apache.org/jira/browse/JS2-527
Project: Jetspeed 2
Type: Improvement
Components: Security
Versions: 2.1, 2.1-dev
Reporter: Ate Douma
Assigned to: Ate Douma
Fix For: 2.1, 2.1-dev
By default, Jetspeed supports hierarchical names for role, group and user principal names and uses the '.' (dot) as a path or level separator.
But right now (if ever) Jetspeed own admin portlets don't really use or support hierarchical principal definitions, even if the security model and component can handle it.
Furthermore, and this is a major problem for some, because of this email addresses can't be used for user account names.
By making hierarchical interpretation of principal (user,role and group) names optional, this now becomes possible.
As we don't use factories for instantiating the principal classes, and I didn't want to cause a lot of api changes, I've opted for
simple static methods on each principal type class through which this can be turned off.
And by using Spring MethodInvokingFactoryBeans this can easily be configured through spring assembly.
I'll add a new spring assembly file doing just that for all three principal classes but then commented out so by default everything stays the same.
One example from this assembly file (hierarchical-principal-names.xml):
<bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
<property name="staticMethod">
<value>org.apache.jetspeed.security.impl.UserPrincipalImpl.useHierarchicalNames</value>
</property>
<property name="arguments">
<value>false</value>
</property>
</bean>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-527) Allow email addresses to be used for user
accounts by making hierarchical interpretation of principal names optional
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-527?page=all ]
Ate Douma updated JS2-527:
--------------------------
Summary: Allow email addresses to be used for user accounts by making hierarchical interpretation of principal names optional (was: Allow email addressed to be used for user accounts by making hierarchical interpretation of principal names optional)
correcting a small typing error
> Allow email addresses to be used for user accounts by making hierarchical interpretation of principal names optional
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-527
> URL: http://issues.apache.org/jira/browse/JS2-527
> Project: Jetspeed 2
> Type: Improvement
> Components: Security
> Versions: 2.1, 2.1-dev
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.1, 2.1-dev
>
> By default, Jetspeed supports hierarchical names for role, group and user principal names and uses the '.' (dot) as a path or level separator.
> But right now (if ever) Jetspeed own admin portlets don't really use or support hierarchical principal definitions, even if the security model and component can handle it.
> Furthermore, and this is a major problem for some, because of this email addresses can't be used for user account names.
> By making hierarchical interpretation of principal (user,role and group) names optional, this now becomes possible.
> As we don't use factories for instantiating the principal classes, and I didn't want to cause a lot of api changes, I've opted for
> simple static methods on each principal type class through which this can be turned off.
> And by using Spring MethodInvokingFactoryBeans this can easily be configured through spring assembly.
> I'll add a new spring assembly file doing just that for all three principal classes but then commented out so by default everything stays the same.
> One example from this assembly file (hierarchical-principal-names.xml):
> <bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
> <property name="staticMethod">
> <value>org.apache.jetspeed.security.impl.UserPrincipalImpl.useHierarchicalNames</value>
> </property>
> <property name="arguments">
> <value>false</value>
> </property>
> </bean>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Closed: (JS2-527) Allow email addresses to be used for user
accounts by making hierarchical interpretation of principal names optional
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-527?page=all ]
Ate Douma closed JS2-527:
-------------------------
Resolution: Fixed
Done
> Allow email addresses to be used for user accounts by making hierarchical interpretation of principal names optional
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-527
> URL: http://issues.apache.org/jira/browse/JS2-527
> Project: Jetspeed 2
> Type: Improvement
> Components: Security
> Versions: 2.1, 2.1-dev
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.1, 2.1-dev
>
> By default, Jetspeed supports hierarchical names for role, group and user principal names and uses the '.' (dot) as a path or level separator.
> But right now (if ever) Jetspeed own admin portlets don't really use or support hierarchical principal definitions, even if the security model and component can handle it.
> Furthermore, and this is a major problem for some, because of this email addresses can't be used for user account names.
> By making hierarchical interpretation of principal (user,role and group) names optional, this now becomes possible.
> As we don't use factories for instantiating the principal classes, and I didn't want to cause a lot of api changes, I've opted for
> simple static methods on each principal type class through which this can be turned off.
> And by using Spring MethodInvokingFactoryBeans this can easily be configured through spring assembly.
> I'll add a new spring assembly file doing just that for all three principal classes but then commented out so by default everything stays the same.
> One example from this assembly file (hierarchical-principal-names.xml):
> <bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
> <property name="staticMethod">
> <value>org.apache.jetspeed.security.impl.UserPrincipalImpl.useHierarchicalNames</value>
> </property>
> <property name="arguments">
> <value>false</value>
> </property>
> </bean>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org