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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.