The userinfo endpoint is an OIDC/OAuth protected resource where client applications can retrieve claims, or assertions, about the logged in end-user. Clients must present a valid access token to retrieve the userinfo claims.

The userinfo endpoint is:

Example of a userinfo response:

GET /openid/userinfo HTTP/1.1
Authorization: Bearer 0f0935c3-a997-40fb-89c2-f7da126ba5d9

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

    "sub": "76a7a061-3c55-430d-8ee0-6f82ec42501f",
    "dataporten-userid_sec": [
    "name": "Andreas \u00c5kre Solberg",
    "email": "",
    "email_verified": true,
    "picture": ""

The set of information that will be available from userinfo depends on which scopes the client has authorized and requested in the authorization request.

Included for backward compatibility. Same as dataporten-userid_sec.

Secondary user IDs, e.g. Feide identifier.

The scopes userid-feide, userid-nin, userid-social and eidas determine what information is included here.

Email address of the authenticated user. Requires the email scope.
true if email is included.
The name of the authenticated user. Requires the profile scope.
A picture of the authenticated user, if available. Requires the profile scope.
The internal ID of the authenticated user. This ID is stable but opaque, not releasing any additional information about the user. Always included.