IDPv3.1.2 LDAP connector: using two distinct LDAP servers?

[Guenther Schreiner]

Hello altogether,

 Currently we're trying to use two distinct LDAP server clusters which serve completely independent user groups.
 With the help of
	https://wiki.shibboleth.net/confluence/display/IDP30/LDAPAuthnConfiguration#LDAPAuthnConfiguration-AggregateDNResolver
 we have tried to setup an IDP providing information of the two user groups.

 In fact, we have recognized that the only LDAP server specified by the parameter
	idp.authn.LDAP.ldapURL
 is used whereas the parameters
	idp.authn.LDAP.ldapURL1 and idp.authn.LDAP.ldapURL2
 are simply ignored within the usage of the four different pools (bindSearchConnectionPool1, bindSearchConnectionPool2,
bindConnectionPool1,
 bindConnectionPool2). All of them depend on the bean "connectionConfig" with more specific definitions of p:ldapUrl.

 Does anyone has got the same problem?

With best regards,
 Guenther
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6336 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20160601/e66cb05d/attachment-0001.p7s>