Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-1244

Create a Crowd SSO authenticator that will allow Customers to be authenticated from the local directory

    XMLWordPrintable

Details

    • 4
    • 38

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      How to configure JSD and Crowd SSO

      If you use Atlassian Crowd and its single sign-on (SSO) capabilities to manage users:

      • In order for public signup to work, in JIRA, set the Crowd permission to be Read/Write. To do this, go to User management > User directories.
      • When configuring who can authenticate to JIRA via Crowd, if you have customers that do not belong to groups, make sure you select the setting that allows all users in the directory to authenticate. See Mapping a Directory to an Application.

      For more information, please read: Managing customers

      Crowd Licensing

      Atlassian Crowd is a separate product and therefore if you wish to use Crowd for SSO, you will need to purchase a Crowd license that is large enough for your user base. Customers in JIRA Service Desk, while free in JIRA Service Desk, will consume a license in Crowd.

      When you enable Crowd SSO for JIRA, you will only be able to authenticate as users from the Crowd server and users from the internal JIRA directory can’t authenticate to access JIRA. This means both paid JIRA users, agents and free JIRA Service Desk customers need to be users in Crowd.

      It’d be useful to create a new authenticator that knows about JIRA Service Desk Customers in the internal JIRA directory and authenticate them differently from JIRA users.

      Such a change would require changes to Crowd, JIRA and JIRA Service Desk. There are currently no plans to undertake this work in the next 6-12 months. If you are interested in this feature, please watch, vote and add a comment with your specific use case.

      Attachments

        Issue Links

          blocks

          Suggestion - JSDCLOUD-630 SSO integration with JIRA Service Management

          • Closed
          is related to

          Suggestion - JSDCLOUD-1498 JIRA Service Desk Authentication Documentation

          • Closed

          Suggestion - JSDSERVER-1244 Create a Crowd SSO authenticator that will allow Customers to be authenticated from the local directory

          • Gathering Interest
          relates to

          Suggestion - JSDCLOUD-1025 Service Desk login does NOT respect use of custom Seraph Authenticator

          • Closed

          Suggestion - JSDCLOUD-1052 Crowd does not recognize agent based pricing for Service Desk Customers

          • Closed

          Suggestion - CWD-4116 Crowd does not recognize Service Desk Customers as distinct from JIRA users

          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              7ad1551c39c0 Benjamin Paton
              ezhang Ed Zhang (Automation)
              Votes:
              155 Vote for this issue
              Watchers:
              109 Start watching this issue

              Dates

                Created:
                Updated: