nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question about Crowd and OAuth/Single User Sign-On

Alfred Darakjian

We currently have JIRA SD and Confluence under our belt. I had a few questions:

- Does Crowd come with using JIRA SD for free or is it another entity with it’s own license? Would we need Crowd in order to handle OAuth/Single-User sign-ons with regards to 3rd party applications?

Basically, the premise is we have our own 3rd party app we’re building and we’d like to implement OAuth with our Atlassian products. This means that users who sign-on to our 3rd party App should be automatically signed in to JIRA SD/Confluence when they navigate to it from our 3rd party App via hyperlinks or what not... How can this be done?

- If we were to license crowd, how much extra would that cost on top of our JIRA/Confluence licenses?

Accepted answers

Michael Bachmann_1dy59l

Crowd is it's own separate product with separate licensing, the prices are all listed on it's product page: Crowd pricing

With Crowd you are able to integrate your own applications and then enable SSO for all other connected applications as per the documentation:

Specifically:
You only need to log in once, to Crowd or a Crowd-connected application. When you start another Crowd-connected application, you will be logged in automatically.
When you log out of Crowd or one of the Crowd-connected applications, you will be logged out of Crowd and the other application(s) at the same time.

You can find more details on how to actually implement this in the documentation Integrating Crowd with a Custom Application

All comments

Michael Bachmann_1dy59l

Crowd is it's own separate product with separate licensing, the prices are all listed on it's product page: Crowd pricing

With Crowd you are able to integrate your own applications and then enable SSO for all other connected applications as per the documentation:

Specifically:
You only need to log in once, to Crowd or a Crowd-connected application. When you start another Crowd-connected application, you will be logged in automatically.
When you log out of Crowd or one of the Crowd-connected applications, you will be logged out of Crowd and the other application(s) at the same time.

You can find more details on how to actually implement this in the documentation Integrating Crowd with a Custom Application

Alfred Darakjian

Thanks for the information Michael. I've actually learned that we need to use Atlassian Access since we're on the Cloud. The problem is we're concerned about customer O-Auth, not so much Agent O-Auth. Does that mean we'd have to pay for every external customer that uses our support dashboard? Can we even have O-Auth with Access?

Michael Bachmann_1dy59l

Oh sorry I have completely overlooked the cloud tag

My answer applies to the server products only as there is no Crowd on Cloud, the corresponding counterpart is, as you already mentioned, the new Atlassian Access which is very different to Crowd.

Sadly I don't have much experience with the Atlassian Cloud or Atlassian Access, but from what I have found so far Atlassian Access currently only supports Atlassian products and is primarily meant to manage your users in your own company, not your customers.

But generally you don't have to pay for customers (meaning Jira Service Desk Customers).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

jira-service-desk

jira-cloud