# SCIM Deprovisioning Issue

**URL:** <https://devforum.okta.com/t/scim-deprovisioning-issue/34044>\
**Category:** SCIM\
**Created:** [July 30, 2025, 4:53am UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044 "2025-07-30T04:53:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijay](https://avatars.discourse-cdn.com/v4/letter/v/4bbf92/32.png) [@vijay](https://devforum.okta.com/u/vijay)\
**Post date:** [July 30, 2025, 4:53am UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044/1 "2025-07-30T04:53:18Z")

</div>

Hi Team,

We are implementing Scim for our application. While testing de provisioning we encounter case

1. User de provision from Okta (User deactivated which resulted in removing user from scim provisioned app).
2. PUT request with active flag false sent to our app.
3. Our app logic fails for some reason (it may get failed due to server down, any of the internal services not avaiable)
4. Our app sends error to Okta. Problem starts here since user is removed from okta scim app but its still active in our app since request failed.

This creates dangling user issue, is their anything that Okta recommends to do for such case since we were in assumption that failure for user deactivation will again reassign user in okta

---

<div class="post-metadata">

**Author:** ![ramgan](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@ramgan](https://devforum.okta.com/u/ramgan)\
**Post date:** [July 30, 2025, 2:08pm UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044/2 "2025-07-30T14:08:32Z")

</div>

I understand that you don’t see the unassigned user under **Application \> Assignments** Tab. For these errors, you can use **Dashboard \> Tasks \> Application accounts need deprovisioning** section to select and retry sync for failed user deprovisioning tasks.

---

<div class="post-metadata">

**Author:** ![vijay](https://avatars.discourse-cdn.com/v4/letter/v/4bbf92/32.png) [@vijay](https://devforum.okta.com/u/vijay)\
**Post date:** [August 1, 2025, 4:50am UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044/3 "2025-08-01T04:50:37Z")

</div>

Thanks, by this way we can retry again for deprovision same user but how would end user come to know that user deprovisioning is failed. When i encounter this issue i did not see any notification that user deprovisioned failed. is their any way to know this or notification from Okta that tells user about failure. I do know that checking logs can tell u but end user wont be checking logs everytime.

---

<div class="post-metadata">

**Author:** ![vijay](https://avatars.discourse-cdn.com/v4/letter/v/4bbf92/32.png) [@vijay](https://devforum.okta.com/u/vijay)\
**Post date:** [August 1, 2025, 5:00am UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044/4 "2025-08-01T05:00:27Z")

</div>

I have also encounter issue for Group Provisioning. **description** attribute value is coming as null from Group Post request even though it is mapped in Okta Groups Profile. We created group → added group name and group description but when i push group value for description is null in post request. is their anything specific that needs to be done because i am getting displayname correctly.

Request recieved from Okta

ScimGroupRequest {  
displayName = ‘scimGroup4’,  
schemas = [  
‘urn:ietf:params:scim:schemas:core:2.0:Group’  
],  
members = [  
ScimSubCategory.Member {  
value = ‘f2a3b9d1-8f64-4d83-bb0e-a7d43b372c9e’,  
display = ‘scimvjtest@test.com’  
}  
],  
description = ‘null’  
}

Attaching image of Group attribute mapping. I cant edit them as well so not sure what can be done

 ![Screenshot 2025-08-01 at 10.24.22 AM](https://global.discourse-cdn.com/oktadev/original/2X/e/e614d282e34ff8f6142429b68fe7043ec0d8ca58.png)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [August 31, 2025, 5:00am UTC](https://devforum.okta.com/t/scim-deprovisioning-issue/34044/5 "2025-08-31T05:00:37Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.