View Issue Details

IDProjectCategoryView StatusLast Update
0003912SymmetricDSNew Featurepublic2019-04-23 15:41
Reporterpmarzullo Assigned Topmarzullo  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.10.1 
Target Version3.10.1Fixed in Version3.10.1 
Summary0003912: LDAP Base DN specification should be able to provide more than one LDAP tree for searching (fixed in 3.8 using 0003910)
DescriptionRight now, the LDAP Base DN only allows one location to search in the LDAP tree for authenticating users.

Need to provide a way to be able to specify more than one Base DN value.
Additional InformationThe code has been changed to allow the specification of more than one Base DN by separating the Base DN specification by a "|" (pipe symbol).

For example, to specify just one Base DN:

ou=Users,o=IT,c=US,dc=corp,dc=local

To specify more than one Base DN:

ou=Users,o=IT,c=US,dc=corp,dc=local|ou=Users,o=Tech,c=US,dc=corp,dc=local
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.10 b3eb819b

2019-04-10 15:13:31

Philip Marzullo

Details Diff
0003912: LDAP Base DN specification should be able to provide more than
one LDAP tree for searching
Affected Issues
0003912
mod - symmetric-assemble/src/asciidoc/configuration/ldap.ad Diff File

Issue History

Date Modified Username Field Change
2019-04-10 15:33 pmarzullo New Issue
2019-04-10 15:33 pmarzullo Status new => assigned
2019-04-10 15:33 pmarzullo Assigned To => pmarzullo
2019-04-10 15:33 pmarzullo Issue generated from: 0003911
2019-04-10 19:14 pmarzullo Status assigned => resolved
2019-04-10 19:14 pmarzullo Resolution open => fixed
2019-04-10 19:14 pmarzullo Fixed in Version => 3.10.1
2019-04-10 19:14 pmarzullo Summary LDAP Base DN specification should be able to provide more than one LDAP tree for searching => LDAP Base DN specification should be able to provide more than one LDAP tree for searching (fixed in 3.8 using 0003910)
2019-04-10 20:00 Changeset attached => SymmetricDS 3.10 b3eb819b
2019-04-23 15:41 elong Status resolved => closed