Hi everyone,
We have shipped an integration with OKTA to enable Atlassian Access customers to connect to LDAP servers at no additional cost.
Regards,
The Atlassian Access team
Hi everyone,
As Dave mentioned in the last update, we’ve implemented User provisioning with SCIM and you can use this mechanism to automate user and group provisioning.
As a quick summary:
- We currently support Okta, OneLogin, and Azure AD.
- For other identity providers, you can use the User provisioning (SCIM) API (documentation at developer.atlassian.com) to sync users and groups over to Atlassian products.
With regards to single sign-on, we support SAML SSO and you can find the instructions to the supported Identity Providers on the linked documentation page.
Regards,
The Atlassian Access team
Hi everyone,
We're pleased to announce that documentation for the User provisioning (SCIM) API is now available on developer.atlassian.com. The API is an implementation of the SCIM specification and is intended to be used to sync users and groups from an identity provider to an Atlassian organization. Once you have linked an Atlassian Cloud site (like example.atlassian.net) to your organization, users and groups will be synced to your site and you can use them to control access to Jira and Confluence Cloud as well as permissions within those products. Learn more about how automatic user provisioning works with Atlassian Cloud.
There are several key benefits to automating user provisioning for Atlassian Cloud:
- It saves you time as an administrator by automating the process of creating and removing Atlassian accounts for your users
- It improves security by reducing errors in the provisioning/deprovisioning process
- It can help reduce costs by ensuring you are not billed for users who are no longer active
The SCIM API is intended for customers who are not already using one of our supported identity providers. We currently support Okta and are actively working on support for Azure Active Directory and Onelogin. If you are using one of these identity providers, we recommend using the supported Atlassian app for these identity providers as this will simplify the configuration process.
We're actively working in this area and will share another update when support for additional identity providers is available.
Regards,
Dave Meyer
Atlassian Access Product Management
- is duplicated by
-
ID-6218 Would like to incorporate an Active Directory Login
- Closed
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
CSP-147262 You do not have permission to view this issue
- was cloned as
-
- Closed
- links to
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[ID-79] Support LDAP integration with Cloud
Narmada, Your link doesn't work, although I have found that https://www.okta.com/partners/atlassian/. It took me some time to gain knowledge of how to connect AD on-premise with Jira Cloud but thank to this ticket -> Okta choice I think I will be able to do so (reduced cost in comparison to Azure AD).
Hi everyone,
We have shipped an integration with OKTA to enable Atlassian Access customers to connect to LDAP servers at no additional cost.
Regards,
The Atlassian Access team
Need to spend an additional 22K to get this annually for a site of 1400 users!. No thank you. https://confluence.atlassian.com/cloud/pricing-and-billing-for-atlassian-access-948237309.html
This sounds promising but I'm still confused and need to understand how to handle user management and SSO with other systems (e.g. a BI tool embedded in a confluence app) when you don't own a domain and users are not from the same organization.
also posted to the community as well as we're at a total loss here https://community.atlassian.com/t5/Confluence-questions/Atlassian-Cloud-user-management-and-SSO-for-external-not-in-our/qaq-p/1031628
Do we need to subscribe to "Atlassian Access" for each user for $3.00/month to "help reduce costs by ensuring you are not billed for users who are no longer active" i.e. save $7.00 when someone leaves the company (doesn't happen very often)?
In that case, I don't think that I will do much savings...
Narmada, is there another ticket somewhere to have Atlassian provide an LDAP solution built into the core product? This seems like a miss on the part of Atlassian to only have this feature as a HUGE additional expense to purchase licenses for Atlassian Access. Many other similar tools have LDAP / Azure AD integration as part of their core packages. Please advise if this is on list for future builds. Thank you.