Does Jira Product Discovery Contributors need an Atlassian Access license if I want them to use SSO?

[Simon Huprich]

Hi everyone,  

My question would be if I can enforce SSO to Contributors (without an Access Licence and without product access).

Because in my case I have about 5000 users with product access (Jira, Confluence) and Access licenses. But also another 5000 users with no license at all, but with the same claimed domain. All the 10.000 users should be able to act as Contributors.

Can I enforce SSO to have the same security standards for everyone?

Regards
Simon

[Tanguy Crusson · Accepted solution]

For SSO you need Atlassian Access. If a user account in Atlassian Access only has the contributor role and no other product access they're not going to be billed.

[Tanguy Crusson]

To be 100% sure, here's what you can do: 

• Make the changes to make sure the users you want as contributors are configured like that
• Go to admin.atlassian.com - Billing
• In there you'll see "Atlassian Access" with a number of users - and price estimate, which will apply next billed date
• If it doesn't work like you expect, revert your changes and please let us know!

[Simon Huprich]

Hi @Tanguy Crusson

Thank you for your answer.

We followed your suggestion and here are my observations:

• We created an AD-Contributor Group, which got synced from AD to Atlassian. 
• We added this group as "JPD Contributor Group" (Settings => Project => JPD => Access)
• A test user which is part of this AD-group is shown under "managed accounts" as "non-billable", with "no product access", "invited" but without (?) a group membership. 
• The same test user is part of the default auth policy where SSO is enforced

BUT this specific user can not access the Jira Product Discovery, not even the Atlassian site. It seems that nobody in the AD-Contributor Group can access at the moment unless they have - coincidentally - product access to some Atlassian product. 

Would it be possible to get connected in a more direct way? (Support-ticket, site-access, etc.). 

[Tanguy Crusson]

yeah, I guess the problem is that part: 

> but without (?) a group membership. 

The user needs to be part of the contributor group for this to work.

Can you please raise a support ticket? From Jira Product Discovery, left sidebar, "give feedback", "get help from the support team". 

The team can help you troubleshoot this

[Nate Whitehead]

I think Atlassian needs to configure a SSO for Contributors feature much like the SSO for JSM Cusotmers feature launched in the last year. This would likely close this gap.