portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Closed: (JS2-503) UserManager's setUserEnabled() method fails after creating new users
Date Fri, 14 Apr 2006 19:05:00 GMT
     [ http://issues.apache.org/jira/browse/JS2-503?page=all ]
     
Ate Douma closed JS2-503:
-------------------------

    Fix Version: 2.1
                 2.1-dev
     Resolution: Fixed

Confirmed and fixed.

Also found the same incorrect usage of SecurityAccess.getInternalUserPrincipal in DefaultUserSecurityHandler.addUserPrincipal
 
Thanks for finding this one Grant!



> UserManager's setUserEnabled() method fails after creating new users
> --------------------------------------------------------------------
>
>          Key: JS2-503
>          URL: http://issues.apache.org/jira/browse/JS2-503
>      Project: Jetspeed 2
>         Type: Bug

>   Components: Security
>     Versions: 2.0-FINAL
>  Environment: Windows XP
>     Reporter: Grant Gochnauer
>     Assignee: Ate Douma
>      Fix For: 2.1, 2.1-dev

>
> If I create a new user using the Admin component
> (_portalAdmin.registerUser(user.getEmailAddress(), user.getPassword(), user.getRoles(),
user.getGroups(), null, profilingRules, null);
> and then call the UserManager's setUserEnabled method, it will fail because it cannot
find the user
> (_userManager.setUserEnabled(user.getEmailAddress(), false);)
> I stepped through the source code and it appears that in the method:
> org.apache.jetspeed.security.spi.impl.DefaultUserSecurityHander.updateUserPrincipal(UserPrincipal
userPrincipal) is calling
> InternalUserPrincipal internalUser = securityAccess.getInternalUserPrincipal(fullPath,
false); which instead of a fullpath needs to be passed a username instead. So what happens
is that it tries to find a user with "/user/myuser@blah/com" instead of "myuser@blah/com".
> I have confirmed that after calling the registerUser method, the user does exist in the
database and there is no reason that the InternalUserPrincipal object should be coming back
null in the updateUserPrincipal method described above.

-- 
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


Mime
View raw message