[MGNLLDAP-83] Support for more than one LDAP server Created: 13/May/14  Updated: 28/Jan/19  Resolved: 01/Jul/14

Status: Closed
Project: LDAP Connector
Component/s: None
Affects Version/s: 1.6.2
Fix Version/s: 1.6.3

Type: Bug Priority: Major
Reporter: Frank Sommer Assignee: Milan Divilek
Resolution: Fixed Votes: 3
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLLDAP-92 LDAP authentication on multiple AD do... Closed
is related to DOCU-525 Support for more than one LDAP server Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In http://documentation.magnolia-cms.com/display/DOCS/LDAP+Connector+module is described, that you can use the LDAP module with version 1.4 for the access to various LDAP server. But the module 1.4 doesn't work with Magnolia 5 (tested with 5.2.4). The following exception occures, because of API changes in M5.

14-05-12 11:43:40 WARN  AUTHOR[ajp-bio-0.0.0.0-8009-exec-6]info.magnolia.jaas.sp.ldap.LDAPAuthenticationModule: Exception caught
java.lang.UnsupportedOperationException: Use manager to modify this group
  at info.magnolia.cms.security.MgnlGroup.getAllGroups(MgnlGroup.java:132)
  at info.magnolia.jaas.sp.ldap.LDAPAuthenticationModule.collectGroupNames(LDAPAuthenticationModule.java:260)
  at info.magnolia.jaas.sp.ldap.LDAPAuthenticationModule.updateJCRGroups(LDAPAuthenticationModule.java:231)
  at info.magnolia.jaas.sp.ldap.LDAPAuthenticationModule.setEntity(LDAPAuthenticationModule.java:181)



 Comments   
Comment by Milan Divilek [ 12/Jun/14 ]

Introduced ability to defined more than one ldap or ad property file.

Additional property files can be declared in magnolia.properties file with this pattern jndi.ldap.config.<realmName> where realmName corresponds with realm name of the UserManager.
If no specific property file is defined for the UserManager realm then the default configuration, defined under jndi.ldap.config, is used.

Comment by Jan Haderka [ 20/Jun/14 ]
public static String getJNDIConfig(final String realName){}

Can you rename that property to realmName? Current name is confusing if you see just method signature w/o javadoc.

Generated at Mon Feb 12 02:21:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.