Grégory Joseph wrote:
So, two things: 1) this problem has been fixed more generally with MAGNOLIA-3037[1]. This is available in the trunk (4.3-m1, 4.3-snapshot). It could be backported to the 4.2 branch too, but there are no plans to do a new 4.2 release soon. 2) in all cases, if you need to access more user properties than the basic name, fullName and language, you will need to extend info.magnolia.jaas.sp.ldap.LDAPAuthenticationModule#setEntity to push the desired properties into the Entity object, and the info.magnolia.cms.security.ExternalUserManager/info.magnolia.cms.security.ExternalUser pair to expose it. (and register the UserManager appropriately [2]). As of yet, we have no one-size-fits-all solution for this, so depending on your projects' needs, this might be simple (if all you need is read those properties) or complex (if you also need to manage ldap users via Magnolia)
We plan on going live with our first Magnolia site in a couple of weeks. We'll have to see how we deal with this. Do you have any idea on the timeframe for a 4.3 release?
Nils. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
