Creation of new portal user into LDAP fails - not given role 'Authenticated' and password coded incorrectly ----------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1261 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1261 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha2 Environment: AS 4.0.5.GA, Portal 2.6-alpha2, Win XP, Oracle 9i, OpenDS Reporter: Ian White Create a new portal user, either self register or do it via as the admin user. 2 problems stop the new user logging in: - The user gets created in my OpenDS repository, and is assigned the 'User' role, but not the 'Authenticated' role. - The password won't work 2 manual fixes are required before that user can login: - Using an LDAP GUI (JXeplorer), add the new user to the 'Authenticated' role (by adding a member attribute) - Using an LDAP GUI, change the password tp what it was supposed to be (get encoded again) Now you can login as that new user. Another way to do the above fixes without having to use an LDAP GUI is to create the new user using the admin account, then using the role and user portlets, assign the required roles to the new user and then change the new users password. QUESTION - why does there have to be that additional role ''Authenticated'anyway ?

Creation of new portal user into LDAP fails - not given role 'Authenticated' and password coded incorrectly ----------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1261 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1261 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha2 Environment: AS 4.0.5.GA, Portal 2.6-alpha2, Win XP, Oracle 9i, OpenDS Reporter: Ian White Attachments: Ians-OpenDS-tree.jpg, jboss-service.xml, ldap_identity-config.xml, login-config.xml Create a new portal user, either self register or do it via as the admin user. 2 problems stop the new user logging in: - The user gets created in my OpenDS repository, and is assigned the 'User' role, but not the 'Authenticated' role. - The password won't work 2 manual fixes are required before that user can login: - Using an LDAP GUI (JXeplorer), add the new user to the 'Authenticated' role (by adding a member attribute) - Using an LDAP GUI, change the password tp what it was supposed to be (get encoded again) Now you can login as that new user. Another way to do the above fixes without having to use an LDAP GUI is to create the new user using the admin account, then using the role and user portlets, assign the required roles to the new user and then change the new users password. QUESTION - why does there have to be that additional role ''Authenticated'anyway ?

Creation of new portal user into LDAP fails - not given role 'Authenticated' and password coded incorrectly ----------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1261 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1261 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha2 Environment: AS 4.0.5.GA, Portal 2.6-alpha2, Win XP, Oracle 9i, OpenDS Reporter: Ian White Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Beta1 Attachments: Ians-OpenDS-tree.jpg, jboss-service.xml, ldap_identity-config.xml, login-config.xml Create a new portal user, either self register or do it via as the admin user. 2 problems stop the new user logging in: - The user gets created in my OpenDS repository, and is assigned the 'User' role, but not the 'Authenticated' role. - The password won't work 2 manual fixes are required before that user can login: - Using an LDAP GUI (JXeplorer), add the new user to the 'Authenticated' role (by adding a member attribute) - Using an LDAP GUI, change the password tp what it was supposed to be (get encoded again) Now you can login as that new user. Another way to do the above fixes without having to use an LDAP GUI is to create the new user using the admin account, then using the role and user portlets, assign the required roles to the new user and then change the new users password. QUESTION - why does there have to be that additional role ''Authenticated'anyway ?