-
Bug
-
Resolution: Answered
-
Low
-
None
-
2.1
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
Original Description:
The scenarios is as follows:
Imagine a company has 50 users Crowd, JIRA, confluence plus other apps. All applications are using Crowd SSO. This company purchased 10 agents JSD. When a customer is added, it is created in the JIRA local directory. Since Crowd SSO is enabled, this customer cannot login. This company cannot add customer accounts into Crowd directory as they have not enough seats.
- is related to
-
JSDSERVER-1052 Crowd does not recognize agent based pricing for Service Desk Customers
- Closed
-
- Closed
-
- Gathering Interest
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
- was cloned as
-
DESK-3676 Loading...
[JSDSERVER-923] JIRA + JSD 2.0 + Crowd (SSO) - Customers can't log in
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 157808 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 651304 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 651203 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 651203 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305427 ] | New: JAC Bug Workflow v3 [ 3126470 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Priority | New: Low [ 4 ] |
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.
| Workflow | Original: JSD Bug Workflow v5 [ 2059393 ] | New: JSD Bug Workflow v5 - TEMP [ 2305427 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056834 ] | New: JSD Bug Workflow v5 [ 2059393 ] |
I’m really unhappy with this issue
We are rolling out the same confirmation onto a network for 250 users. We are able rolling out jira service desk to support this installation. For this we started with 25 jira service deck agents. The plan was then to all AD user as jira customer. This then let all AD user raise service desk issues. As we already use and are happy with crowd we went with crowd. We got crowd to 500 user to covert the 250 full users.
All our jira customer are full AD users. One of the reasons to go with jira and jira service is within jira you don’t pay for jira customer. For a number of reasons we can’t use local jira users. And we don’t want users to sign up. All users are already in AD.
I’m unhappy with “Workaround” for this problem. Crowd should support jira customers without taking a crowd license. I see this as a bug and not a new feature
tps://jira.atlassian.com/browse/JSDSERVER-1052 – invalid/resolved#
https://jira.atlassian.com/browse/CWD-4116 - won’t fix/ resolved
what I’m really unhappy with is the workaround to pay for more crowd licenses. Pay for the next licence step in crowd + $7000 one off and support each year +£3500. Just to support are AD jira customer
that’s also +$3500 each year to support a bug. That’s move than we paid for crowd to start with. Just to support jira serve desk customer. We have already have paid for crowd for cover are full users.
The other workaround is not to use crowd for jira but I have already paid for crowd. I will still need to pay for crowd to support or other Atlassian application.
In over 20+ years of working with applications I have never had to pay to work around a bug/problem. And then pay over the licenses cost each year for a bug that is not fixed and no time scale to be fixed. This was sold as don’t pay for jira service desk customers. But for use we need to pay $7000 more one off and then +$3500 each year to support jira service desk customers. That makes no sense!