Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1717

Customers Cannot Login if using Crowd Server and closed Application

    XMLWordPrintable

Details

    Description

      If you have "public sign-up" turned on, users are created in the Crowd directory not the Internal directory (assuming the Crowd directory is at the top of the user directories list).

      If your crowd directory application is "closed", meaning you have setup Groups that are allowed to login to Jira (not the entire directory), then the user will not e able to login to the service desk as they cannot authenticate to the Crowd application.

      there is no way to establish a "Default Group" for customers except to establish a default group in the Crowd Directory Application for new users.

      In any case, creating customers in Crowd is a NON-STARTER. There is no way I can afford the license to do so.

      See JSD-1716

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-42418 Allow Internal users to login with SSO enabled

          • Gathering Interest

          Suggestion - JSDSERVER-1716 Directory for Customers

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSDSERVER-1720 Customers Cannot Login with SSO Enabled

          • Highest - Our top priority issues
          • Closed

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

          • Closed

          Suggestion - JSDSERVER-5437 Indicate in JSD when customer is in Crowd and has no permission to authenticate

          • Closed

          Activity

            People

              Unassigned Unassigned
              b8a4333cf7d7 James Rogers
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync