Internal Directory with LDAP Auth not working,Too many users using LDAP

Doing a test set up. If I set up as LDAP or AD (LDAP as well) and set it up as follows ....

Base DN - dc=foo,dc=bar,dc=tld
...
Additional Group DN - CN=jiraUsers,OU=GroupA,OU=InternalGroups

... it works, but it dumps our whole directory into the users

If I do Internal with LDAP Auth (**PREFERRED**) using the following:

Base DN - CN=jiraUsers,OU=GroupA,OU=InternalGroups,dc=foo,dc=bar,dc=tld

I can't get it to authenticate ... using 'copy user on login' or not.

I need it to only authenticate users in that group ... Any ideas why the second one wouldn't work or how I can get it to only sync/import the users in that group?

2 answers

OK, so this one is similar to this (looking at catalina.out):

https://answers.atlassian.com/questions/25711/ldap-not-woking-in-delegated-ldap-configuration-in-jira-4-3-4

But there's not final answer posted there. I'm evaluating, so I don't have a support contract. Anyone dealt with this?

Here's the stack trace:

2012-04-27 10:18:25,822 http-8080-8 ERROR anonymous 618x47627x1 1scf4qc 192.168.115.165 /rest/gadget/1.0/login [springframework.ldap.control.AbstractRequestControlDirContextProcessor] No matching response control found for paged results - looking for 'class javax.naming.ldap.PagedResultsResponseControl

2012-04-27 10:18:25,822 http-8080-8 ERROR anonymous 618x47627x1 1scf4qc 192.168.115.165 /rest/gadget/1.0/login [crowd.manager.application.ApplicationServiceGeneric] Directory 'Delegated LDAP Authentication' is not functional during authentication of '*****'. Skipped.

2012-04-27 10:18:25,822 http-8080-8 ERROR anonymous 618x47627x1 1scf4qc 192.168.115.165 /rest/gadget/1.0/login [jira.security.login.JiraSeraphAuthenticator] Error occurred while trying to authenticate user '*****'.

com.atlassian.crowd.exception.runtime.OperationFailedException

at com.atlassian.crowd.embedded.core.CrowdServiceImpl.convertOperationFailedException(CrowdServiceImpl.java:869)

at com.atlassian.crowd.embedded.core.CrowdServiceImpl.authenticate(CrowdServiceImpl.java:79)

at com.atlassian.crowd.embedded.core.DelegatingCrowdService.authenticate(DelegatingCrowdService.java:35)

at com.atlassian.crowd.embedded.core.FilteredCrowdServiceImpl.authenticate(FilteredCrowdServiceImpl.java:43)

at com.atlassian.jira.security.login.JiraSeraphAuthenticator.crowdServiceAuthenticate(JiraSeraphAuthenticator.java:75)

at com.atlassian.jira.security.login.JiraSeraphAuthenticator.authenticate(JiraSeraphAuthenticator.java:40)

....

Hi,

Which LDAP container are your users in? If CN=jiraUsers,OU=GroupA,OU=InternalGroups,dc=foo,dc=bar,dc=tld is a group and not a container under which the users are located then using that as a Base DN won't work as JIRA won't be able to see any of your LDAP users.

You need to configure the Base DN to a container high enough in your LDAP tree so that all the users that you want to use JIRA will be in its container or one of its sub-containers, e.g. OU=InternalUsers,dc=foo,dc=bar,dc=tld You should be able to limit which users can then use JIRA by using something along the lines of (&(objectCategory=Person)(sAMAccountName=*)(memberOf=jiraUsers)) as the User Object Filter - http://confluence.atlassian.com/display/JIRA/Connecting+to+an+LDAP+Directory

Hope that helps?

Andrew.

In the internal Jira Directory with LDAP Authentication ....

even setting the base DN to the root (just dc=foo...) doesn't work. Neither does

OU=InternalUsers,dc=foo ...

Tried the same with LDAP (Active Directory) and ...

Base DN of

OU=InternalUsers,dc=foo,dc=bar,dc=tld

... AND ...

(&(objectCategory=Person)(sAMAccountName=*)(memberOf=jiraUsers))

in User Schema ...

Neither of them work.

No errors in catalina.out either way. The only thing that seems to work is putting users directly into the OUs and pointing directly to those OUs (no very scalable or flexible)

That's strange, it should be subtree searching.

When you were using "copy user at login" were you also specifying jira-users as a default group? It would need that mapping as users need to be in jira-users to be able to log in.

Yes, I did have that set up.

I also tried sAMAccountName as the 'User Name RDN Attribute' as well as 'cn' ... but no dice.

I've bought my license, so I will be filing a ticket with them.

Thanks ...

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

419 views 7 5
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