LDAP: error code 34 - 0000208F: NameErr: DSID-031001F7, problem 20 06 (BAD_NAME)

 

2 answers

1 accepted

@Nic Brough [Adaptavist] It turns out it is a bad DN, as you said in your answer.

AD has a bug apparently, where replication "clashes" can cause odd entries to be generated in AD.  In this case, we found three offending entries which looked like this:

 

Some-valid-looking-groupname
CNF:57759099-0d22-4168-b16d-4dea649a0123

 

The carriage return is no mistake.  This is pasted straight out of the AD Users and Computers CPL, and the group name includes a CR.

Removing these offending groups made JIRA happy.  They could also probably be filtered out as seen in some of the support articles, since they have "CNF:" in common.

1 vote

You're feeding it a broken domain name (DN)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,345 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot