Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1015

Upgrading from Crowd 1.2.x to 1.3.2 does not populate RDN value in existing OpenLDAP directories.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • 1.3.2
    • Directory - LDAP
    • None

      Not having a User RDN in Crowd 1.3.2 throws the following exception when adding a new user:

      Caused by: javax.naming.InvalidNameException: Invalid name: =donnamcgahan,o=sgi,c=us; remaining name '=donnamcgahan,o=sgi,c=us'
	at javax.naming.ldap.Rfc2253Parser.parseAttrType(Rfc2253Parser.java:130)
	at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:83)
	at javax.naming.ldap.Rfc2253Parser.parseDn(Rfc2253Parser.java:45)
	at javax.naming.ldap.LdapName.parse(LdapName.java:772)
	at javax.naming.ldap.LdapName.<init>(LdapName.java:108)

      This User RDN value should be auto-populated on upgrade with cn.

              doflynn David O'Flynn [Atlassian]
              donna@atlassian.com DonnaA
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: