Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

User info

This page must be considered part of the iSHARE Framework

This page is considered normative and is therefore compliant with RFC 2119.

OpenID Connect 1.0 endpoint for obtaining attributes of a Human Service Consumer conforming to the scope defined in the access token.

Request

HTTP methods

  • POST

Parameters

Example

> Authorization: Bearer IIeDIrdnYo2ngwDQYJKoZIhvcNAQELBQAwSDEZMBcGA1UEAwwQaVNIQ
< Content-Type: application/json; charset=UTF-8

POST /connect/userinfo

Response

Headers

  • Content-Type

    String.

    Defines response body content type. MUST be equal to application/jwt.

HTTP status codes

  • 200 OK

    When a valid request is sent, an OK result should be returned.

  • 400 Bad Request

    When an access token is valid, but the request itself is invalid.

  • 401 Unauthorized

    When Authorization The header is either missing, invalid, or the token has already expired.

Parameters

Since response Content-Type is application/jwt it should be expected to retrieve a signed JWT. JWT should be iSHARE compliant, and its payload should contain delegation evidence. In addition, the JWT payload might also contain the following parameters:

  • organisationIdentifier

    String. (Required)

    Identifier of the organisation that the user is representing. MUST be ETSI/X.509 OrganizationIdentifier (OID 2.5.4.97) issued by a Trust Service Provider (TSP), using the format in ETSI EN 319 412-1 V1.5.1, clause 5.1.4: <3-letter type><2-letter country>-<identifier>

200 OK Example

Decoded JWT Payload

PreviousAccess tokenNextM2M Verifiable Credential Endpoints

Last updated