Hi everyone,

We're closing this request as a duplicate of ACCESS-577, which will provide an improve audit log of user managements across Atlassian Cloud sites (including user invitations and changes to group memberships). We consider API access for this audit log within the scope of that issue, so when it is available, we will announce it there.

We're closing this issue because the scope of the request is specifically around an API for reporting on changes. If you are interested in an API for managing users and groups in Jira Cloud, 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 on the SCIM API feature request (ID-6305) when support for additional identity providers is available.

Regards,
Dave Meyer
Atlassian Access Product Management

Hi varsha.mane976916654,

The update user experimental API in JIRA Cloud has recently been removed. Please see https://jira.atlassian.com/browse/JRACLOUD-66936?focusedCommentId=1609545&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1609545 for details.

Thank you,

Diego

Hi Diego

As per latest https://docs.atlassian.com/jira/REST/cloud/  document, update user api not found.

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-updateUser this api not found in document.

Can you please confirm that update user is not supporting in future?

Thanks

Varsha

Hi varsha.mane976916654, I'm sorry to hear that you are still having problems with JIRA's REST API. It is possible that error has the same root cause as https://jira.atlassian.com/browse/JRACLOUD-67118 . Please watch or comment on that issue.

Thank you.

Hi Diego

We are facing issue while deleting group as well using jira cloud rest api's.
We are facing error while deleting group.
Error Code: 400 with
{"errorMessages":["Cannot delete group, as all directories are read-only."],"errors":{}}

Please let me know what is wrong here?

Thanks
Varsha

Thanks Diego, we will check ID-6305 for update..

Hi Varsha,

We have not announced a release date for those new APIs, sorry. We understand that you are not the only customer who would like to have supported and standard user management APIs. Please watch ID-6305 to receive updates as soon as they are available.

We also understand that group/membership management is an important requirement and we will take that into consideration as part of ID-6305.

Thank you.

Hi Diego

Thanks for this information..
But by when will have new Atlassian SCIM User Management APIs.
Also want to know that, do we have same api's for Group as well like add user to group and remove user from group.

Thanks
Varsha

Hi Varsha,

I am sorry to hear that you are still experiencing issues with the JIRA User Management APIs. Unfortunately those APIs are currently marked as "experimental" and they may be eventually superseded by new Atlassian SCIM User Management APIs. Please watch ID-6305 for updates.

Thank you.

Hi Diego

Any updates on below comment..
I have already raised ticket for this issue here
https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-617

and discussing same topic here : https://community.developer.atlassian.com/t/jira-cloud-api-failing-on-free-active-version/5613
One more issue we are facing that, while creating user we need to send notification email to user so we are passing notification:true in request body of create user. We are getting response successful to create user but in response we aren't getting email address..
If we remove notification parameter then we are getting email address in response..
Please help us as these are blocking issues for us..

Thanks
Varsha

Got it, voted.

Thanks Adarsh.

Hi ekarahasan,

We have an open request for this, please watch and vote this ticket. for further updates.

thanks,

Adarsh

Are there any plans to make the user management APIs for Atlassian Cloud compliant with the SCIM standard? 

A standards-based access to user attributes and entitlements would enable us to more easily migrate into and manage our users on your platform. 

Background: SCIM (System for Cross-domain Identity Management) is the open API for managing identities. The specification is now complete and published under IETF.

For more info: https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management

P.S. Other large SaaS service providers like SalesForce already provide SCIM compliant APIs.

Thanks.

Hi Diego

I have already raised ticket for this issue here

https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-617

and discussing same topic here : https://community.developer.atlassian.com/t/jira-cloud-api-failing-on-free-active-version/5613

One more issue we are facing that, while creating user we need to send notification email to user so we are passing notification:true in request body of create user. We are getting response successful to create user but in response we aren't getting email address.. 

If we remove notification parameter then we are getting email address in response..

Please help us as these are blocking issues for us..

Thanks

Varsha

Hi varsha.mane976916654,

Could you please raise an JIRA Cloud Support ticket so we can assist you investigating those problems with the JIRA REST API?

Thank you.

Hello

We are using JIRA cloud rest api's in our application.

We are using api's for Create,Update,Delete and Get User and Group with group members.

We are using basic authentication, authentication user is sysadmin of JIRA cloud instance.

Also we are trying these api's using free version of JIRA cloud if account expired then we are creating new one to test rest api's.

But from last one month we facing unstable behavior with above user and group and group member api's.

Sometime all are failing with 401 unauthorized error or 500 internal server error.

But Update user and update group member is continuously failing from last one month.

This is something blocker issue in our application..

We are aware that these are experimental api's, wanted to know that when will have fixed behavior of these api's..

We are reffering these api's

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-createUser

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-updateUser

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-removeUser

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-getUser

Please help to fixed these issues..

Thanks

Varsha

Bump.

set active/deactivate sure is needed as most of the user management

It's not hard piece of work to develop, why no one actually look at this?

This should not be defined as minor, it should be critical.

I'd like to use this to synchronise LDAP user accounts, since it doesn't look like AOD-1837 will be done any time soon.

I'd definitely use this to build a script to de-activate all users who have not been active for > 6 months. Managing licenses in nearly impossible in our instance given volume of users.

Managing users with the interface is painfully slow.