We're running Jira 6.2 with Crowd providing authentication services across all our Atlassian software. Crowd syncs with Active Directory, and our users can all log in to Atlassian software using their Windows logon.
When a user tries to login to Jira, the first attempt fails - a message saying "You do not have permissions to log in ....." appears above the username field in the login page. When the user then tries again with the same username and password they successfully log in.
I believe (but cannot be certain) that this behavior began after the upgrade to Jira 6.2. Confluence doesn't seem to exhibit this behavior, and neither does Stash
Has any one else had the same problem?
When integrating JIRA with Crowd, the SSO is not enable by default, additional modification to seraph file is needed to enable it and some customers decide to user other softwares to provide SSO.
Do you have any kind of SSO configuration in place? I'm asking this because I see you mentioned Windows logon, perhaps are you refering to Integrated Windows Authentication?
If you have SSO enabled, can you turn it off temporarily and see if it brings any improvement?
SSO hasn't been enabled.
Our users log on to Atlassian applications using their Windows credentials - this has been working fine until just recently.
I'm beginning to get more reports from users about permissions - one user can no longer resolve issues, an admin-level user can not assign issues.
When I try to clone a Zephyr issue only a popup showing the issue id and nothing more shows. On the browser console I see: RTE not registered Error: No jira/editor/registry at c...
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