Authenthification is very Slow

Question

Dear all,

we have huge Performance problems in login process to JIRA. We use a LDAP Connection to Microsoft Active Directory. Here are some lines of the log during authentification.

2016-06-24 15:35:40,045 http-bio-80-exec-225 INFO anonymous 935x242926x2 8x2zld XX.XXX.XXX.XX /login.jsp [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=Firma,dc=local took 10017ms 2016-06-24 15:35:50,093 http-bio-80-exec-225 INFO anonymous 935x242926x2 8x2zld xX.XXX.XXX.XX /login.jsp [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=Firma,dc=local took 10007ms

RVal · Answer

* User Management can be still done in AD groups even if you use Crowd as a proxy in between JIRA and AD if that is something you want to try.
* Network problems still may be the reason because it depends where your JIRA server is installed. It could that JIRA server is located in different network segment (different office) compared to other tools. It's best to capture packets with Wireshark to make sure.
* It could be also problems with AD connector configuration in JIRA
* Another possibility is too elaborate permission configuration on who can login / browse issues

Jonas Fitz · Answer

I don't think that it is a Network or LDAP issue, because all other application in our company using AD in the same way are very performant. We do not see the need of an additional tool like crowd, because we prefer, that usermanagement for JIRA will be done within Active Directory Groups by our IT-support.

Do you think ther could be network problems nevertheless we don't know about problems within our other tools.

RVal · Answer

Could be network or LDAP issues. Did you try to to capture packets (with Wireshark) and see how long it takes LDAP to respond after request is sent from JIRA ? You can try to put Crowd server in  between and make sure connection between your JIRA and Crowd is quick. Crowd in turn will synch up users from LDAP but it should not affect JIRA.