[jira] [Updated] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19632:
--
Fix Version/s: 2.4.3
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19632:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 7e0097501daa5177ee38450b3a9f0e47d7ebf1a7
Author: Robert Levas
Date: Fri Jan 20 12:38:27 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit ecc1cc2acc6a0fa6121d7e4692f295853392edfe
Author: Robert Levas
Date: Fri Jan 20 13:22:11 2017 -0500
{noformat}
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19632:
--
Attachment: AMBARI-19632_trunk_01.patch
AMBARI-19632_branch-2.5_01.patch
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19632) Ldap sync fails when there are special characters in distinguished names
[
https://issues.apache.org/jira/browse/AMBARI-19632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19632:
--
Status: Patch Available (was: Open)
> Ldap sync fails when there are special characters in distinguished names
>
>
> Key: AMBARI-19632
> URL: https://issues.apache.org/jira/browse/AMBARI-19632
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: ldap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19632_branch-2.5_01.patch,
> AMBARI-19632_trunk_01.patch
>
>
> Ldap sync fails when there are special characters in distinguished names.
> For example if there was a user with the distinguished name of
> {{OU=test/test,OU=users,DC=EXAMPLE,DC=COM}} and that user was a member of a
> synced group, then the lookup of the user using the membership attribute in
> the group would fail due to the special character.
> The error would look something like
> {noformat}
> REASON: Caught exception running LDAP sync. Uncategorized exception occured
> during LDAP processing; nested exception is javax.naming.NamingException:
> [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012
> (DIR_ERROR), data 0
> ]; remaining name 'OU=test/test,OU=users,DC=EXAMPLE,DC=COM'
> {noformat}
> *Solution*
> Update the library versionf for Spring LDAP
> * {{org.springframework.security/spring-security-ldap}} to {{4.0.4.RELEASE}}
> * {{org.springframework.ldap/spring-ldap-core}} to {{2.0.4.RELEASE}}
> Then use {{LdapUtils.newLdapName}} to convert a String representing a DN into
> a {{javax.naming.ldap.LdapName}} and use that object in the search facility
> executed in
> {{org.apache.ambari.server.security.ldap.AmbariLdapDataPopulator#getFilteredLdapUsers(java.lang.String,
> org.springframework.ldap.filter.Filter)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
