Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

LDAP: Search DN could not be parsed

I have successfully setup and tested LDAP configuration. However in the logfile I get regular error messages:

2018-01-12 00:10:04,586 ERROR [https-jsse-nio-7990-exec-6] @OKY1IHx10x55560x0 10.120.16.12,10.120.16.12 "GET /scm/test/mytest.git/info/refs HTTP/1.1" c.a.c.directory.ldap.name.SearchDN User Search DN could not be parsed
javax.naming.InvalidNameException: Invalid name: (|(ou=technical)(ou=users)),ou=auth,ou=mycompany,o=data

This is strange as the LDAP Configuration can be successfully tested in the gui. Here are my settings

LDAP Schema:

  • Base DN:ou=mycompany,o=data
  • Additional User DN: (|(ou=technical)(ou=users)),ou=auth
  • Additional Group DN: ou=approles,ou=roles

User Schema Settings:

  • User Object Filter: (objectclass=inetOrgPerson)

 

In a related post I have noticed the following comment

combine the "Base DN" + "Additional User DN" should not contain a filter format. 

I have have tested the following combination with no success

LDAP Schema:

  • Base DN:ou=mycompany,o=data
  • Additional User DN: ou=auth
  • Additional Group DN: ou=approles,ou=roles

User Schema Settings:

  • User Object Filter: objectclass=(&(inetOrgPerson)(|(ou=technical)(ou=users)))

Ends in Test retrieve user : Failed

 

How do I configure LDAP corrrectly to get rid of the error message in the log?

2 answers

Thanks to atlassian support team I could solve the problem: The issue is mentioned in the following knowledge base article:

Changing the configuration as follows fixed the problem:

LDAP Schema:

  • Base DN:ou=mycompany,o=data
  • Additional User DN: ou=auth
  • Additional Group DN: ou=approles,ou=roles

User Schema Settings:

  • User Object Filter: (&(objectclass=inetorgperson)(|(ou:dn:= technical)(ou:dn:=users)))

 

Reference: How to write LDAP search filters

I had the same error message and I ended up resolving mine but completely removing the additional user DN information.

thanks for pointing me in the correct direction.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

1,922 views 0 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you