User:Justapersona/SCIM

System for Cross-domain Identity Management (SCIM) is an open standard for automating the exchange of user identity information between identity domains, or IT systems.

For example, as a company hires and fires employees, they are added and removed from the company's electronic employee directory. SCIM could be used to automatically add/delete (or, provision/de-provision) accounts for those users in external systems such as Google Apps for Work, Office 365, or Salesforce.com. Then, a new user account would exist in the external systems for each new employee, and the user accounts for former employees might no longer exist in those systems.

In addition to simple user-record management (creating & deleting), SCIM can also be used to share information about user attributes, attribute schema, and group membership. Attributes could range from user contact information to group membership. Group membership or other attribute values are generally used to manage user permissions. Attribute values and group assignments can change, adding to the challenge of maintiaining the relevant data across multiple identity domains. {{cite book |author = Internet Engineering Task Force, Network Working Group|title = System for Cross-Domain Identity Management: Core Schema|version = Draft 19|date = May 11, 2015|url = http://tools.ietf.org/html/draft-ietf-scim-core-schema-19|accessdate = 2015-05-17}}

The SCIM standard has grown in popularity and importance, as organizations use more SaaS tools.{{cite press release | title = Identity Management Companies To Demonstrate Simple Cloud Identity Management (SCIM) Specification at Internet Identity Workshop (IIW) | publisher = SailPoint | date = October 18, 2011 | url = https://www.sailpoint.com/news/identity-management-companies-to-demonstrate-simple-cloud-identity-manageme | accessdate = May 11, 2015}} A large organization can have hundreds or thousands of hosted applications (internal and external) and related servers, databases and file shares that require user provisioning. Without a standard connection method, companies must write custom software connectors to join these systems and their IdM system.{{cite journal | last = Grizzle | first = Kelly | title = SCIM: Provisioning users, killing connectors | journal = SecureID News | publisher = SecureID | date = March 10, 2014 | url = http://www.secureidnews.com/news-item/scim-provisioning-users-killing-connectors/ | accessdate = May 17, 2015}}

SCIM uses a standardised API through REST with data formatted in JSON or XML.

History

The first version, SCIM 1.0, was released in 2011 by a SCIM standard working group organized under the Open Web Foundation.{{Cite web|url = http://www.simplecloud.info/#overview|title = SCIM Overview|accessdate = May 17, 2015|website = SimpleCloud.info| publisher = Simple Cloud Identity Management }} In 2011, it was transferred to the IETF, and the current standard, SCIM 1.1 was released as IETF RFC in 2012.{{cite web | last = Wilson | first = Neil | url2 = https://www.unboundid.com/blog/author/neil-wilson | title = SCIMming along... | publisher = UnboundID blog | date = June 22, 2011 | url = https://www.unboundid.com/blog/2011/06/22/scimming-along | accessdate = May 11, 2015}}{{cite book | author= Internet Engineering Task Force, Network Working Group | title = System for Cross-Domain Identity Management: Core Schema 1.1 | version = Version 1.1 | date = August 2, 2012 | url = https://tools.ietf.org/html/draft-scim-core-schema-01 | accessdate = 2015-05-11}} The working group in IETF is currently working on SCIM 2.0; draft 19 was published in May, 2015. The standard has been implemented in various IdM software.{{Cite web|url = http://www.simplecloud.info/#implementations|title = Known SCIM 1.1 implementations|date = |accessdate = May 17, 2015|website = SimpleCloud.info|publisher = Simple Cloud Identity Management|last = |first = }}

The standard was initially called Simple Cloud Identity Management (as it is still called this in some places), but the name was officially changed to System for Cross-domain Identity Management (SCIM) when the IETF adopted it.{{cite web | last = Hunt | first = Phil | title = Standards Corner: SCIM and the Shifting Enterprise Identity Center of Gravity | website = Oracle Fusion Middleware (blog) | publisher = Oracle | date = February 27, 2014 | url = https://blogs.oracle.com/fusionmiddleware/entry/standards_corner_scim_and_the | accessdate = May 17, 2015 }}

Interoperability was demonstrated in October, 2011, at the Cloud Identity Summit, an IAM industry conference. There, user accounts were provisioned and de-provisioned across separate systems using SCIM standards, by a collection of IdM software vendors: Ping Identity, SailPoint, Technology Nexus and UnboundID. In March 2012, at IETF 83 in Paris, Interoperability tests continued by the same vendors, joined by Salesforce.com, BCPSoft, WSO2, Gluu, and Courion (nine companies, total).{{cite web | title = Logistics and attendee info for the March 20012 SCIM interop event | website = SCIM, Simple Cloud Identity Management | date = April 26, 2012 | url = https://code.google.com/p/scim/wiki/FirstInteropEvent | accessdate = May 11, 2015}}

SCIM is not the first standard for exchanging user data, but it builds on prior standards (e.g. SPML, PortableContacts, vCards, and LDAP directory services) in an attempt to be a simpler and more widely-adopted solution for cloud services providers.{{cite web| title = SCIM: How It Works| website = PingIdentity.com| url = https://www.pingidentity.com/en/resources/articles/scim.html| format = Article| accessdate = May 11, 2015}}{{cite book | author= Internet Engineering Task Force, Network Working Group | title = System for Cross-Domain Identity Management: Core Schema | version = Draft 19 | date = May 11, 2015 | section = Section 1, Introduction | url = http://tools.ietf.org/html/draft-ietf-scim-core-schema-19#section-1 | accessdate = 2015-05-11}}

References