Interop Best Practice E

From IDESG Wiki
Jump to: navigation, search

<< Back to Baseline Functional Requirements Index

INTEROP-BP-E. RECOMMENDED MODULARITY

Entities SHOULD implement modular identity components in their digital identity management functions.

SUPPLEMENTAL GUIDANCE

This best practice is for IDENTITY-PROVIDERS to offer modular identity solutions for the services and functions they perform relating to digital identity management. "Modular identity solutions" are services that can be used by USERS, RELYING-PARTIES and other participants either individually, or in combination with other modular services from the same or different providers, in order to provide choices and efficiencies in meeting their needs. Often such services are designed and offered around single function, and with STANDARDS-based interfaces that allow them to be composed with other purchased services or the purchaser's own systems.

On the concept of service modularity and composition generally, see: A Practical Guide to Federal Service Oriented Architecture (Federal CIO Council, 2008), at page 16: https://cio.gov/wpcontent/uploads/downloads/2013/03/PGFSOA_v1-1.pdf, and OASIS SOA Reference Model (2006): http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.html

APPLIES TO ACTIVITIES

REGISTRATION, CREDENTIALING, AUTHENTICATION, AUTHORIZATION, INTERMEDIATION

KEYWORDS

ARCHITECTURE, DESIGN, INTEROPERABILITY, OPEN-STANDARDS



Quick Links: SALS | Baseline Functional Requirements v1.0 | Glossary |