We are using
Jira 7.3.3 on a Windows Server 2008 R2 and Bamboo 6.0.3 on a Windows Server 2012 R2. Basicly it works but we have a weird behaviour for several days
Bamboo is configured to use the JIRA Server as User repositories
Which works (synchronization is ok, I see the Users/groups in the Bamboo user list)
Most users in JIRA are setup to authenticate via LDAP (Active Directory) which also works fine on the JIRA server.
But if i try to logon to Bamboo only the user with no LDAP configuration works (our Admin User) for all other users the authentication fails with wrong username password.
I checked the logfiles but I'm not able to find anything suspicious.
The only thing where I know it was changed, was the IP Adress of the Bamboo server but the new one is also in the JIRA user server whitelist.
So what can i do now?
Where are the "wrong" login attempts logged?
Few things we can test to narrow down the issue:
log4j.appender.com.atlassian.user.impl.ldap=DEBUGAfter restart try to login again and see the logs for errors.
Set this in (bamboo-install/atlassian-bamboo/WEB-INF/classes/log4j.properties) and restart your bamboo
After all these, if you still can't figure out the issue, I would recommend logging a ticket with the support to investigate further.
* there is only one entry, I configured it via Bamboo UI and there is only one selection possible (not like in JIRA where you can have several user directories)
* I enabled it
now I have the error
2017-10-11 16:10:52,980 ERROR [http-apr-8085-exec-1] [DefaultUserAccessor] Error in getUser():com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://xxxxxxxxxx:8080/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1
com.atlassian.user.EntityException: com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://insv01104:8080/rest/usermanagement/1/search?entity-type=group&start-index=0&max-results=-1
Which is funny because As far as i understand this has nothing to do with LDAP
I add the content of the crowd.properties
probably there is something wrong
xxxx is the right servername
and application.name and password are also ok
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot