You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 78 Next »

The Additional Information service (aka: Userinfo) provides claims about the authenticated user beyond what is contained directly in the ID Token. The set of supported scopes and claims are described in the following section, followed by a description of consent handling for the supported scopes. The specific type of Access Token that is required to get access to the Additional Information service is also described.


The following table summarizes how the Additional Information service impacts relevant functions of the OIDC Provider:

FunctionImpact
IDP optionsAll supported options are availble to the OIDC Client
Authorize endpointAdds support for a small set of non-standard scopes and claims
Token endpointAdds support for a specific type of by-reference access token
Resource endpoint(s)Implements the Userinfo endpoint

Scopes and claims

The Userinfo endpoint supports an additional set of claims about the end user beyond the basic set of claims included in the ID Token. The set of additional claims returned via Userinfo depends on the scopes requested by the OIDC Client. Four different configurations are supported as suggested by the below table, corresponding to the standard scopes emailphone and  address and the non-standard scope nnin

Note that the basic set of claims about the end user from the ID Token are duplicated in the Userinfo response. Such duplicated claims are not shown in the table. The standard claims sub and updated_at are always returned in the Userinfo response.

Supported claims are marked (tick) wheras  (warning)  indicates future support. Claims that require consent from the end user are marked (thumbs up)Non-standard claims are marked (info) and are specific for the OIDC Provider from BankID.  See a separate list of unsupported standard claims. 

The OIDC Provider from BankID supports signed responses from Userinfo

ClaimSupportExampleDescriptionCommentEditorial comment
sub(tick)9578-5999-4-1765512Subject Identifier  
updated_at(warning)1468582440Update timeEpoc time of latest update of any data element behind any of the supported claimsMust be added
Email ( scope = email )
email(warning) (thumbs up) Preferred email Must be added
email_verified(warning) Email verification status Must be added
Phone ( scope = phone )
phone_number(tick) (thumbs up)95871775Preferred phone numer  
phone_number_verified(tick)falsePhone number verification statusDepending on the source for the number. Numbers for BankID on Mobile are regarded as verified.Numbers from other sources may also be regarded verified.
all_phone_numbers(info) (thumbs up){{"number":"95871775","number_verified":false},{"number":"46897469","number_verified":false},{"number":"94782958","number_verified":false}}All phone numbers with verification status  
Address ( scope = address )
address(tick) (thumbs up){ "formatted": "Lybekkveien 11C\n0772 Oslo\nNorway", "country": "Norway", "street_address": "Lybekkveien 11C", "postal_code": "0772", "locality": "Oslo", "house_number": "11", "house_letter": "C", "street_name": "Lybekkveien" }Postal addressStandardized claim with both standardized and non-standard sub-claims 
address.formatted(tick) (thumbs up)Lybekkveien 11C\n0772 Oslo\nNorwayFull mailing address  
address.street_address(tick) (thumbs up)Lybekkveien 11CFull street address  
address.locality(tick) (thumbs up)OsloCity or locality  
address.postal_code(tick) (thumbs up)0772Postal code  
address.country(tick)NorwayCountry  
address.street_name(info) (thumbs up) Lybekkveien

 Street name component from street_address

 To be reviewed
address.house_numer(info) (thumbs up) 11House number component from street_address To be reviewed
address.house_letter(info) (thumbs up) CHouse letter component from street_address To be reviewed
National Identity Number ( scope = nnin )
nnin(info) (thumbs up)181266*****Norwegian National Identity Number (fødselsnummer)  

Consent handling

TBC

Characteristics of Access Token

The Userinfo  endpoint demands an Access Token of the bearer type with the proper characteristics to grant access. Appropriate tokens are returned from the Token endpoint. A token of this kind has a generic nature, meaning that it grants access to any of the claims supported by Userinfo. The service behind Userinfo performs Introspect to determine (among other things) that it is the correct audience for the incomming token and also the specific set of claims that the token should gain access to. The following set of token attributes are returned by introspection for this particular kind of access token:

TODO: hvilke av disse støtter vi over Introspect og hvilke verdier gjelder for Access Tokens for Userinfo-tjenesten

AttributeExampleDescription
active xxxx
scope xxxx  
client_id xxxx  
username xxxx  
token_type xxxx  
exp xxxx  
iat xxxx  
nbf xxxx  
sub xxxx  
aud xxxx  
iss xxxx  
jti xxxx  


 

  • No labels