16e3e9eaf982 find rest calls details below

REST End Point: /rest/usermanagement/1/user?username=xxxxx
 

{     
   "name": "xxxxx",
   "first-name": "aaa",
   "last-name": "bbb",
   "display-name": "ccc" 
}

Hi 5ca6434febe4, can you post the JSON you are sending to the Crowd API endpoint?

Best regards

Sebastian

 -Dcrowd.email.change.by.external.apps=true  not worked  for us and we are using crowd Version: 5.3.1

Crowd version: 5.3.1, I am trying to update user details except email but still getting below error, what kind of design is this??
 

{     "reason": "APPLICATION_PERMISSION_DENIED",      
      "message": "External applications are not allowed to change user emails"
 }

For me  -Dcrowd.email.change.by.external.apps=true has not worked (crowd Version: 5.0.1)

The same error occurs when trying to activate/deactivate user, e.g. using the sample curl as described here https://confluence.atlassian.com/crowdkb/how-to-deactivate-activate-a-user-through-api-814197032.html gives error 403 {"reason":"APPLICATION_PERMISSION_DENIED","message":"External applications are not allowed to change user emails"}

Why it gives error on changing email, if the parameters have only name and active:
 
'{"name":"testuser", "active":"false"}'?

That is blocker for my API scripts for bulk-update users (crowd Version: 5.0.1)

I confirm that setting up JVM parameter -Dcrowd.email.change.by.external.apps=true is a working solution (Crowd DC 5.1.2).

This is a blocker for enabling Cloud Migrations, where we need to bulk/programmatically change the email addresses for users.

@tena-admin Yes it works, we changed this and we are now able to update with our IAM system the email addresses inside of Crowd via the Rest API.

Can Atlassian comment on whether the configuration parameter mentioned in previous comment is supported and can be used to allow external applications change a user's email address?