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
-
CLOUD-1889 Connect Jira Studio Users to external corporate LDAP
- Closed
- is related to
-
ID-182 Ability to Bulk Change Email Domain on Users
- Closed
- relates to
-
ID-6563 Allow mapping Active Directory Groups to Atlassian Cloud Groups
- Closed
-
CSP-147262 Loading...
- was cloned as
-
ID-80 Support SAML integration with Cloud apps
- Closed
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...