Interop Best Practice A

From IDESG Wiki
Jump to: navigation, search

<< Back to Baseline Functional Requirements Index

INTEROP-BP-A. RECOMMENDED PORTABILITY

Entities SHOULD utilize services and systems that allow for identity account portability; specifically:
(a) IDENTITY PROVIDERS SHOULD provide an easy to use method to allow USERS to switch to a new provider(s).
(b) IDENTITY PROVIDERS SHOULD provide departing USERS a mechanism to link their RELYING PARTY accounts with their new provider(s).
(c) RELYING PARTIES SHOULD provide USERS with a mechanism to associate multiple credentials to a single account.
(d) RELYING PARTIES SHOULD provide USERS with a mechanism to have a single account per credential.
(e) IDENTITY PROVIDERS SHOULD utilize services and systems that allow for affordable identity account portability.
(f) Wherever feasible, IDENTITY-PROVIDERS SHOULD provide USERS with a mechanism for portability of their privacy and other USER preferences.

SUPPLEMENTAL GUIDANCE

The term "account portability" means the ability for a USER to move to a different service provider to provide registration, credentialing and authentication services, and authorize the transfer of account information from an original service provider to the chosen provider. Portable identity data should include the following types of information: registration information, credentials, preferences, and associated accounts.

APPLIES TO ACTIVITIES

REGISTRATION, CREDENTIALING, AUTHENTICATION

KEYWORDS

ACCOUNT, CHOICE, INTEROPERABILITY, PORTABILITY, USABILITY



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