ID Token

The OpenID Connect Provider from BankID provides ID Tokens with claims as shown in the below table. The origin column indicates non-standard claims. Such claims are either added by Keycloack or the result of customization made by the OIDC Provider from BankID.

The ID token structure builds on Keycloack. Three different token configurations are supported as suggested by the scope column, corresponding to three different combinations of the standard scopes openid and profile and the custom scope nnin_altsub.

• A Minimum ID Token (scope = openid) that contains a minimum set of claims, among which sub and bankid_altsub are the only claims that are linked to the actual user. A minimum ID Token can be used by OIDC Clients that need to authenticate end-users in an anonumous way. The sub and bankid_altsub values do not identify the user unless they are linked by the OIDC Client to other claims about the end user associated that identifies him more precisely.
• A Regular ID Token (scope = openid profile) that builds on a minimum ID Token by adding claims that identifies the end-user by his name and birthdate.
• A Enchanced ID Token (scope = ....... nnin_altsub) that builds either on a minimum ID Token or a regular ID Token by adding a claim containing the Norwegian National Identity Number of the end-user 

As suggested by the IDP column many claims are present for any IDP whereas other claims are dependent on the particular IDP being used. The Eligibility column indicates if a claim is available for any OIDC client or if specific conditions apply. In the latter case eligible OIDC clients must be configured for access in the provisioning process.

Note that the TINFO value-added service supports even more claims about the end-user beyond those contained in the ID Token. The major difference is that none of the claims contained in ID Tokens demand consent from the end user.  This is in contrast to claims supported by TINFO that is subject to consent handling.

Note finally that the OIDC Provider form BankID supports signed ID Tokens in JWT format. The below table shows claims in the payload part of the JWT. Claims contained in the JWT header are not shown.

urn:bankid:bid;LOA=4

BID

CN=BankID Bankenes ID-tjeneste Bank CA 2,

OU=988477052,O=Bankenes ID-tjeneste AS,

C=NO;OrginatorId=9775;

OriginatorName=Gjensidige Bank RA 1

{
 "certValidFrom": 1554448774000,
 "serialNumber": "1055610",
 "keyAlgorithm": "RSA",
 "keySize": "2048",
 "policyOid": "2.16.578.1.16.1.12.1.1",
 "monetaryLimitAmount": "100000",
 "certQualified": true,
 "monetaryLimitCurrency": "NOK",
 "certValidTo": 1617607174000,
 "versionNumber": "3",
 "subjectName": "CN=Nilsen\\, Frode Beckmann,O=TestBank1 AS,
 C=NO,SERIALNUMBER=9578-6000-4-353032"
}