nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update User Profile via Rest API - Final Words?

ADyPo

Hi,

I can't seem to find a satisfactory answer: is it possible to update a user's profile with a Rest API call?

I feel like these should have worked: https://developer.atlassian.com/cloud/admin/user-management/rest/api-group-users/

However, I keep getting a "forbidden.insufficientScope" / "Insufficient scope for this action" in Postman, even with the "GET Profile" request.

I'm the site admin and the user was created by API, in a Directory that I manage with a domain that I manage on the site. What could be wrong?

Can anyone even just "get" a user's profile with a Rest API call on his instance?

Thank you all in advance,

Best regards,

Dylan

Accepted answers

Andrew Marshall

The bug for this issue has been commented on with a fix that has been deployed. All newly-created API keys should function as expected. I tested this out in my environment and it worked for me.

All comments

Andrew Marshall

I'm running into the same issue. The API key I created works for getting a list of users at the organization level, but trying to manage individual users with the same key returns a 403 with a "forbidden.insufficientScope" error, with one of the "acceptableScoes" being "manage:org". You'd think that if I can see data about my org already that this scope would be granted.

Lumos Yoshikoshi

we have the same exact problem! However up until a few days ago per-user operations were working with the same API keys. Were you able to resolve this?

Andrew Marshall

I opened a ticket with support, and they confirmed today that either 1) docs are incorrect, or 2) something isn't working right internally. They are investigating in detail, and I am awaiting a response.

Lumos Yoshikoshi

Thanks for the quick response Andrew and for opening a support ticket. Would love it if you could keep the forum updated about the status of this issue! Thanks again.

Andrew Marshall

The bug for this issue has been commented on with a fix that has been deployed. All newly-created API keys should function as expected. I tested this out in my environment and it worked for me.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

rest

api

user-management

jira-service-management