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.

            [JSDSERVER-1720] Customers Cannot Login with SSO Enabled

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304417 ] New: JAC Bug Workflow v3 [ 3126462 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]

            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:

            1. Set the JIRA internal directory to be above the Crowd directory on JIRA's user directories page.
            2. Download the the midan-authenticator-1.1.jar from the github releases page.
            3. Copy the .jar in to the [JIRA ROOT]/atlassian-jira/WEB-INF/lib folder
            4. Comment out the CrowdSSO authenticator in the [JIRA ROOT]/atlassian-jira/WEB-INF/seraph-config.xml
            5. Add a new authenticator:
              <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.

            Mark Willcox added a comment - 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: Set the JIRA internal directory to be above the Crowd directory on JIRA's user directories page. Download the the midan-authenticator-1.1.jar from the github releases page. Copy the .jar in to the  [JIRA ROOT] /atlassian-jira/WEB-INF/lib folder Comment out the CrowdSSO authenticator in the  [JIRA ROOT] /atlassian-jira/WEB-INF/seraph-config.xml Add a new authenticator: <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.
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058458 ] New: JSD Bug Workflow v5 - TEMP [ 2304417 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2055617 ] New: JSD Bug Workflow v5 [ 2058458 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1955479 ] New: JSD Bug Workflow v5 - TEMP [ 2055617 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615250 ] New: JSD Bug Workflow v5 [ 1955479 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: publicsignup New: affects-server publicsignup
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1602570 ] New: JSD Bug Workflow v4 [ 1615250 ]
            Marty (Inactive) made changes -
            Component/s New: Atlassian Account [ 35992 ]
            Component/s Original: Invite, Signup, Login, Logout, Reset Password [ 44403 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1398712 ] New: JSD Bug Workflow v2 [ 1602570 ]

              knguyen@atlassian.com Kha Nguyen (Inactive)
              b8a4333cf7d7 James Rogers
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: