The claims returned in an ID Token from the OIDC Provider depends one the scopes requested by the OIDC Client. Two different configurations are supported as suggested by the below table, corresponding to the standard scopes openid and profile.

Note that none of the claims conained in the ID Token demand consent from the end user.  This is in contrast to claims returned by Userinfo.

The OIDC Provider form BankID supports signed ID Tokens.

ClaimSupportExampleDescriptionCommentEditorial comment
Minimum ID Token (scope = openid)  
iss(tick)https://preview.bankidapis.noIssuer Identifier for the Issuer  
sub(tick)9578-5999-4-1765512Subject IdentifierPersonal Identifier from BankID
(Serial number from associated BankID certificate)
 
aud(tick)DotNetClientAudienceAlways includes client_id 
exp(tick)1494144386Expiration timeEpoc time 
iat(tick)1494140787Issuing timeEpoc time 
auth_time(tick)1494140786Authentication timeEpoc time 
nonce(tick)<random value>Nonce  
acr(tick)(warning)4Authentication Context ClassLevel of Assurance (LoA) for IDP option being usedMust be added
amr(tick)BankIDAuthentication Method ReferenceName of IDP option being used 
azp(tick)DotNetClientAuthorized partyEquals client_id 
alg(tick)RS256Algorithm used to sign ID Token  
typ(tick)JWTType of key used to sign ID Token  
kid(tick)bankid-oauthID of key used to sign ID Token  
at_hash(tick)(warning)<hash value>Access Token hash value Must be added. Required for hybrid flow and implicit flow
c_hash(tick)<hash value>Code hash valueHybrid flow 
Regular ID Token (scope = openid profile)
name(tick)Nilsen, Frode BeckmannFull nameCommonName from associated BankID certificate 
given_name(tick)Frode BeckmannGiven name (first name)  
family_name(tick)NilsenSurname (last name)  
preferred_username(tick)Nilsen, Frode BeckmannShorthand name Must be reviewed
birthdate(tick)1966-12-18BirthdateBirthDate from associated BankID certificate 
updated_at(tick)(warning)1468582440Update timeEpoc time of issuing time of associated BankID certificateMust be added