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

Crowd does not recognize agent based pricing for Service Desk Customers

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Invalid
    • None
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Some customers have a large number of customers that they would like to access JIRA Service Desk, but instead of using the JIRA Internal Directory, they would like to utilize Crowd to manage their users. This is most relevant when they want their users to authenticate via Crowd SSO. Currently, they cannot do this and still benefit from agent based pricing. Crowd does not recognize Service Desk Customers as a distinct and separate group from regular JIRA users.

      Atlassian Status

      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.

      A suggestion to to enable both remote Crowd and local authentication in JIRA has been created. Please vote and comment on this issue to communicate your need for a feature such as this JSD-1244

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

            Michael Andreacchio made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 651090 ]
            Michael Andreacchio made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 651071 ]
            Michael Andreacchio made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 651071 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012066 ] New: JAC Suggestion Workflow 3 [ 3650723 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665804 ] New: JAC Suggestion Workflow [ 3012066 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324137 ] New: Confluence Workflow - Public Facing v4 [ 2665804 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052907 ] New: JSD Suggestion Workflow - TEMP [ 2324137 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049537 ] New: JSD Suggestion Workflow [ 2052907 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279278 ] New: JSD Suggestion Workflow - TEMP [ 2049537 ]
            jonah (Inactive) made changes -
            Description Original: Some customers have a large number of customers that they would like to access JIRA Service Desk, but instead of using the JIRA Internal Directory, they would like to utilize Crowd to manage their users. This is most relevant when they want their users to authenticate via Crowd SSO. Currently, they cannot do this and still benefit from agent based pricing. Crowd does not recognize Service Desk Customers as a distinct and separate group from regular JIRA users.

            {panel:title=Atlassian Status|borderColor=#ccc|titleBGColor=#cccccc|bgColor=#ebf2f9}
            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.

            A suggestion to to enable both remote Crowd and local authentication in JIRA has been created. Please vote and comment on this issue to communicate your need for a feature such as this JSD-1244
            {panel}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1052].
              {panel}

            Some customers have a large number of customers that they would like to access JIRA Service Desk, but instead of using the JIRA Internal Directory, they would like to utilize Crowd to manage their users. This is most relevant when they want their users to authenticate via Crowd SSO. Currently, they cannot do this and still benefit from agent based pricing. Crowd does not recognize Service Desk Customers as a distinct and separate group from regular JIRA users.

            {panel:title=Atlassian Status|borderColor=#ccc|titleBGColor=#cccccc|bgColor=#ebf2f9}
            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.

            A suggestion to to enable both remote Crowd and local authentication in JIRA has been created. Please vote and comment on this issue to communicate your need for a feature such as this JSD-1244
            {panel}

              Unassigned Unassigned
              kgrier kitkat (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: