OIDC Background

OIDC stands for Open ID Connect and is an authentication mechanism built on top of OAuth2. The OIDC-related settings used in the Settings provider in the Workbench involve setting up an OIDC Provider (known as Authorization Server in OAuth2 terms) and OIDC Relying Parties that other ICONICS services can use to authenticate against and log into GENESIS64.

Current bot support (e.g., for Alexa, Cortana) within certain ICONICS applications use this. Additional documentation should be available from the bot developer for information on how to configure them to log into GENESIS64 using OIDC. Third-party clients can use this too. However, ICONICS' implementation does not expose all the features of OIDC.

ICONICS' current implementation of OIDC/OAuth follows these specifications:

OpenID Connect Core 1.0 - http://openid.net/specs/openid-connect-core-1_0.html
OpenID Connect Discovery 1.0 - http://openid.net/specs/openid-connect-discovery-1_0.html
OpenID Connect Session Management 1.0 - draft 28 - http://openid.net/specs/openid-connect-session-1_0.html
OAuth 2.0 - http://tools.ietf.org/html/rfc6749
Proof Key for Code Exchange - https://tools.ietf.org/html/rfc7636

The only OIDC Flow that is currently supported is the ‘Authorization Code’ flow. Anyone setting this up should either follow documentation (for example, when setting up the bots) or should already be familiar with OIDC/OAuth2.