-
Bug
-
Resolution: Duplicate
-
Highest
-
None
-
2.3.4
I have two directories. "Jira Internal Directory" and "Atlassian Crowd Directory".
The internal directory is at the "top" and is the default directory. This way, when customers self sign-up, their accounts are created in the jira directory (default directory), not the crowd directory.
When following the instructions to enable SSO by changing the Authenticator
<authenticator class="com.atlassian.jira.security.login.SSOSeraphAuthenticator"/>
Users can no longer authenticate to the "Internal Jira Directory" because the authenticator doesn't check the internal directory.
- duplicates
-
JSDSERVER-1244 Create a Crowd SSO authenticator that will allow Customers to be authenticated from the local directory
- Gathering Interest
- is related to
-
JSDSERVER-1717 Customers Cannot Login if using Crowd Server and closed Application
-
- Closed
-
-
CWD-2417 CROWD - JIRA integration does not synchronize custom user attributes / LDAP attributes
-
- Long Term Backlog
-
-
JRASERVER-42418 Allow Internal users to login with SSO enabled
- Gathering Interest
-
JSDSERVER-1716 Directory for Customers
- Gathering Interest
- relates to
-
JSDSERVER-1052 Crowd does not recognize agent based pricing for Service Desk Customers
- Closed
For anyone else who has only recently run in to this, ridiculous, issue; I have just made use of the MIDANAuthenticator courtesy of Alexander Sebastian Jost's comments back in 2016.
I can confirm the MIDANAuthenticator still works and I am using it with Jira version 7.7.0 and Crowd version 3.1.2
Instructions:
<authenticator class="eu.midan.MIDANAuthenticator"/>
How Atlassian still haven't fixed this is incredible. I guess people paying for crazy crowd licenses to accommodate all of their customers is a disincentive.