ManasaA.64001 (Customer) asked a question.
SCIM User Removal from Group Not Updating via PUT in AIW App (SAML)
We are using a SCIM 2.0 integration created via Okta’s Application Integration Wizard (AIW). We noticed that when a user is removed from a group in Okta, Okta still sends a PUT request with the old user list, including the removed user.
Our SCIM server correctly updates the group and returns the updated members in the GET /Groups/{id} call, but Okta continues to send the same outdated PUT payload.
Example:
Below is the sample payload of Groups before and after user removal from group
- Before removal: "members": [ { "value": "user1" }, { "value": "user2" } ]
- After removal: "members": [ { "value": "user1" }, { "value": "user2" } ]
Okta keeps sending the same outdated PUT payload and the user is never removed.
Please help check why Okta is not updating the PUT payload correctly after user
Hi @ManasaA.64001 (Customer) , Thank you for reaching out to the Okta Community!
If you are leveraging Group Push for this, it might be a limitation of the feature. Please review this doc for details on Push Group functionality.
That being said, custom SCIM app provisioning questions are more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-custom/developer work).
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
This month's AMA topic: Okta Device Access. Ask away today.