You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2015/10/08 17:01:27 UTC
[jira] [Closed] (INFRA-10558) Incorrect LDAP entry?
[ https://issues.apache.org/jira/browse/INFRA-10558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-10558.
-------------------------
Resolution: Fixed
Thanks, entry corrected.
> Incorrect LDAP entry?
> ---------------------
>
> Key: INFRA-10558
> URL: https://issues.apache.org/jira/browse/INFRA-10558
> Project: Infrastructure
> Issue Type: Bug
> Reporter: Sebb
> Assignee: Gavin
> Priority: Minor
>
> I came across some strange behaviour in LDAP.
> Note the encoded entry in the output from the following query:
> ldapsearch -LLL -b ou=groups,dc=apache,dc=org '(cn=bookkeeper)' memberUid
> dn: cn=bookkeeper,ou=groups,dc=apache,dc=org
> memberUid: ivank
> memberUid: sijie
> memberUid: fpj
> memberUid: rakeshr
> memberUid: breed
> memberUid: umamahesh
> memberUid:: amlhbm5hbiA=
> memberUid: robindh
> memberUid: mmerli
> The encoded memberUid turns out to be 'jiannan ', i.e. with a trailing space.
> That does not seem right. AFAICT it is the only such entry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)