Identify the technical architecture requirements to support interoperability of IDs to ensure that a) consumer experience should not be compromised and b) the relying party consumption of IDs should not be over complicated. Particularly to ensure the simultaneous support of centralized Vs decentralized IDs in the ecosystem.

Considerations:

• Relying Parties should be able to discover which Identity Providers are provide compatible digital identity services and what services they provide
• Users should be able to choose which IdP they want to interact with and choose to share their information from
• There should be a standardised way for RPs to make service requests to different types of IdPs (e.g., centralised, decentralised)
• Relying Parties should receive back consistently formatted identity attributes (claims) regardless of which IdP it receives the response from
• IdPs regardless of type should be able to provide evidence and metadata to support identity attributes (claims)
• Solutions should have omnichannel support for: desktop web, mobile web, mobile app (at least last 2 major versions of iOS and Android)
• IdP solutions that are based on mobile apps should support app-to-app, or web-to-app redirects
• IdP solutions based on on mobile apps should provide graceful handling of scenarios where the user does not have the app installed or sign up

This working group is run in collaboration with TechUK

The following organisations are contributing to this working group:

Access Partnership, Barclays, Blockpass, BT, CIFAS, Condatis, Consult Hyperion, DWP, Folio, ID Crowd, ID Works, iLabs, Inidsol, Innovate Identity, Lastline, Lexis Nexis Risk Solutions, Mvine, Octopus, OIX, PIB-d, Raidiam, RBS, Shaping Cloud, TCS, techUK, UK Cabinet Office (GDS), Veridium, Yoti