[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-2039) Navigation header shows incorrect information if user is fetched from DB with LDAP as primary identity store

[Boleslaw Dawidowicz (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPORTAL-2039?page=all ]

Boleslaw Dawidowicz resolved JBPORTAL-2039.
-------------------------------------------

    Fix Version/s: 2.6.6 Final
                   2.7 Final
       Resolution: Done

fixed 

> Navigation header shows incorrect information if user is fetched from DB with LDAP as primary identity store
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-2039
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2039
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.5 SP1, 2.6.5 Final, 2.6.4 Final
>         Environment: JBoss Portal with LDAP configured according to Chapter 19.1 - 'How to enable LDAP usage in JBoss Portal' of the Reference Guide
>            Reporter: Martin Putz
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.6 Final, 2.7 Final
>
>
> JBoss Portal has been set up with LDAP as primary identity store, and DB as fallback store if user cannot be retrieved from LDAP:
> conf/login-config.xml:
> ------------------------
>   <login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="sufficient">
>   [...]
>   </login-module>
>   <login-module code = "org.jboss.portal.identity.auth.DBIdentityLoginModule" flag="sufficient">
>   [...]
>   </login-module>
> User 'admin' does not exist in LDAP, but only in DB. The CMS root user has been changed to match an entry in LDAP:
> portal-cms.sar/META-INF/jboss-service.xml:
> --------------------------------------------------
>   <attribute name="CmsRootUserName">cmsadmin</attribute>  
> When I try to login now with the 'admin' user, this seems to work, but some components still make calls to the LDAPExtUserModuleImpl, as this can be found in the logs:
> DEBUG [org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl] No user found with name: admin
> java.util.NoSuchElementException
> 	at java.util.AbstractList$Itr.next(AbstractList.java:427)
> 	at org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl.findUserByUserName(LDAPExtUserModuleImpl.java:77)
>         ...
> As a result, the header navigation does not reflect that a user is logged in. The 'Login' link is still visible and does not switch to the links normally available when a user is logged in. Access to the admin pages is possible when the admin URL [http://localhost:8080/portal/auth/portal/admin] is entered directly, however.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira