Versions Compared

Old Version 1

changes.mady.by.user Frode Beckmann Nilsen

Saved on

compared with

New Version Current

changes.mady.by.user Frode Beckmann Nilsen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PDOIDC and version xID_Demo_OIDC

The REST API comprises implementation of the OIDC Provider from BankID consists of a set of Endpoints, Tokens, Scopes and Claims according to the  following set of endpoints according to the OpenID Connect 1.0 (OIDC) and OAuth 2.0 (OAuth2) standards.  A key feature of the OIDC platform is to provide uniform handling of Claims with corresponding Consent handling across all supported IDPs. 

The OIDC Provider from BankID does in addition provide a set of JavaScript Connectors being front-end wrappers for the REST API. OIDC Clients should use such connectors because it simplifies integration work and ensures that the REST API is used in the intended way.

Since the OIDC/OAuth standards are  standards. Since these standards are frameworks, any particular implementation of endpoints may make both restrictions and extensions. The OIDC Provider from BankID includes both restrictions by not supporting certain optional parts of the standards and also make extensions by adding non-standard capabilities. See Core Concepts for a closer description of topics like Scopes and claims, ID Tokens, Access Tokens, Consent Handling, etc. that are vital to understand before start using the REST API.

Children Display

 Note the following:

  • The

...

  • above endpoints are general and apply for any IDP and VAS. Endpoints that apply specifically for any particular VAS are described in the corresponding VAS-section.
  • An OIDC Client may use JavaScript connectors associated with each of the supported IDPs as an alternative to direct integration with the REST API. 
  • An OIDC Client needs to authenticate with the OIDC Provider for many of the Endpoints.  
  • The OIDC Provider employs signing and encryption of certain data elements over the REST API. Important examples are signing of ID Tokens and responses from Userinfo.

A separate section provides details on message flow provides an elaborated understanding of message flow both  both over the REST API as such and also the message flow with components behind the REST API. The REST API supports all flows from the OIDC/OAuth2 standards. Children Displayalltrue