SCIM Soft Delete
draft-ansari-scim-soft-delete-00

Document Type Expired Internet-Draft (individual)
Authors Morteza Ansari  , Phil Hunt 
Last updated 2015-09-10 (latest revision 2015-03-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ansari-scim-soft-delete-00.txt

Abstract

The System for Cross-Domain Identity Management (SCIM) specification is an HTTP based protocol that makes managing identities in multi- domain scenarios easier to support through a standardized HTTP service. Among other operations, SCIM defines delete operation where upon successful completion of the call, the SCIM endpoint is supposed to delete the requested object and the object should not be available for future SCIM calls and not used in uniqueness criteria requirements. While this model is sufficient for a number of SCIM implementations, there are cases this simple definition of delete may not meet product or business requirements. For example a service provider may require a user object to continue to exist as other objects/data is linked with it or for billing purposes, etc. For example a cloud file storage mechanism may require to show basic information about who created a given file or modified one even if the user is de- provisioned from the system.

Authors

Morteza Ansari (morteza.ansari@cisco.com)
Phil Hunt (phil.hunt@yahoo.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)