@Benjamin Paton We have ~40k student accounts that this feature would allow us to move off of the SSO setup for our faculty and staff, so we would love to participate in the EAP!
Is there still a spot available to participate to the EAP? We've just set up Atlassian Access and would love to be able to enable SSO for internal and portal only customers.
We are new to Atlassian and are a non-profit with community pricing and currently only free-tier accounts (aka nothing paid) however as a non-profit we have Atlassian Access and with it Okta. We currently enjoy SSO for all our technicians (3) in JSM and for Bitbucket and Confluence. We are looking to add portal users in JSM for our ~2000 AD users. I can sync all of them to Atlassian as right now I manually license/invite users to the paid applications so I think I have the workaround someone mentioned in a prior post but haven't set up the JSM portal yet.
Integration in AD for our ~2000 users is a must have for us and we want all our users to SSO into the portal. We also need contractors and outside helpers to make tickets too without SSO so we must be able to allow them to sign up. I think this too is current functionality.
If anything I mentioned about our needs requires this new functionality, PLEASE add me to the list of folks to try this. I know we aren't paid but we are looking to become paid users and migrate our entire helpdesk to this but this is a deal breaking issue so there's zero sense in paying if the functionality isn't there.
We'd recommend using Internal Atlassian Accounts for any users you expect to also require access to other Atlassian products (e.g. Bitbucket, Confluence). These are likely the employees/technicians you mentioned.
You're able to use your Atlassian Access subscription for SSO with Atlassian Accounts today.
When to use Portal-only Accounts
We'd recommend using External Portal-only Accounts for any users that only need access to JSM to raise tickets. Portal-only Accounts don't have the ability to access other Atlassian products (e.g. Bitbucket, Confluence). In your scenario the "contractors" and "outside helpers" are best suited to Portal-only Accounts.
In future you will be able to decide if you wish to authenticate Portal-only Accounts with:
Email + Password
SSO
Email + Password & SSO
Portal-only Account SSO is currently under development and will be available shortly.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
We are a company with about 200 employees. Now we want the employees to access the portal via SSO without first creating an Atlassian account to be able to create tickets. Is this currently possible or is the described here exactly the purpose for this? If this is exactly the intended use for this, we would like to register for the EAP.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
66 comments