Content
View differences
Updated by Christophe Bliard 6 months ago
After all users with deleted status must be hidden both from UI and API v3.
<br>
This is needed for compliance with SCIM specification: if a user is deleted, it must be immediately deleted from an external point of view
[https://datatracker.ietf.org/doc/html/rfc7644#section-3.6](https://datatracker.ietf.org/doc/html/rfc7644#section-3.6):
> Clients request resource removal via DELETE. Service providers MAY choose not to permanently delete the resource but MUST return a 404 (Not Found) error code for all operations associated with the previously deleted resource. Service providers MUST omit the resource from future query results. In addition, the service provider SHOULD NOT consider the deleted resource in conflict calculation. For example, if a User resource is deleted, a CREATE request for a User resource with the same userName as the previously deleted resource SHOULD NOT fail with a 409 error due to userName conflict.
<br>
This is needed for compliance with SCIM specification: if a user is deleted, it must be immediately deleted from an external point of view
[https://datatracker.ietf.org/doc/html/rfc7644#section-3.6](https://datatracker.ietf.org/doc/html/rfc7644#section-3.6):
> Clients request resource removal via DELETE. Service providers MAY choose not to permanently delete the resource but MUST return a 404 (Not Found) error code for all operations associated with the previously deleted resource. Service providers MUST omit the resource from future query results. In addition, the service provider SHOULD NOT consider the deleted resource in conflict calculation. For example, if a User resource is deleted, a CREATE request for a User resource with the same userName as the previously deleted resource SHOULD NOT fail with a 409 error due to userName conflict.