iSHARE Developer Portal
Other resources
Version 2.1 (current version)
Version 2.1 (current version)
  • Welcome to the iSHARE Developer Portal
  • Introduction
    • Getting started
      • Test certificates
      • Test participants
      • Postman collections
    • Release info
    • Help & support
    • Specific technical standards
      • JSON Web Token (JWT)
      • OAuth 2.0
      • OpenID Connect 1.0
      • PKI
      • TLS
      • XACML 3.0
      • Caching
      • DID
      • UTC
      • X.509
      • HTTP response codes
    • UI Guidelines
    • Conformance test tool
  • Roles
    • Roles
  • All roles (common endpoints)
    • Access token (M2M)
    • Capabilities
  • Authorisation Registry Role
    • Getting started
    • Access token (M2M)
    • Capabilities
    • Delegation
    • Delegation Policy
  • Entitled Party
    • Getting started
  • Identity Provider
    • Getting started
    • Authorize
    • Login
    • Access token
    • User info
    • Capabilities
  • Participant Registry role
    • Getting started
    • Access token (M2M)
    • Capabilities
    • Parties
    • Parties (single party)
    • Trusted list
    • Versions
    • Data Spaces
    • Create Entitled Party / Service Consumer
  • Service Consumer Role
    • Getting started
  • Service Provider Role
    • Getting started
      • Service
    • Access token (M2M)
    • Capabilities
    • Return
  • Reference
    • iSHARE JWT
      • Client Assertion
    • Authentication
    • Authorization
    • Authorisation rules
Powered by GitBook
LogoLogo

  • Cookie Policy

  • Privacy Policy

  • Imprint

  • Contact Us

Copyright © 2024 iSHARE Foundation

On this page
  • Request
  • Response
  1. Identity Provider

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 conform scope defined in 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 request itself is invalid.

  • 401 Unauthorized

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

Parameters

  • first_name

    String. Optional.

    First name of the human who’s access token is used.

  • last_name

    String. Optional.

    Last name of the human who’s access token is used.

  • gender

    String. Optional.

    Gender of the human who’s access token is used. Available values are male, female, TBD.

  • company_id

    String. Optional.

    TBD.

  • company_name

    String. Optional.

    TBD.

200 OK Example

< Content-Type: application/jwt

example TBD

Decoded JWT Payload

{
    "example": "TBD"
}
PreviousAccess tokenNextGetting started

Last updated 2 months ago

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

iSHARE compliant
delegation evidence