GET 
/conformance/v3/issuer-mock/.well-known/openid-credential-issuer

Client or Wallet must obtain the Credential Issuer metadata prior to the transaction using strategies described in OAuth 2.0 Authorization Server Metadata or out-of-band.

Request

Responses

200

OK

application/json

Schema

Schema

credential_issuer URLrequired

REQUIRED. The issuer's server identifier, which is a URL that uses the "https" scheme and has no query or fragment components. Authorisation Server metadata is published at a location that is ".well-known" according to RFC 5785 [RFC5785]. If the issuer server acts as an Authorisation Server, this identifier is also used as the Authorisation Server identifier.

Note: If the 'authorization_server' claim is not present, Credential Issuer is also acting as Authorisation Server. AS configuration is defined by the 'OpenID Connect Authorisation Server Metadata'

authorization_server URL

OPTIONAL. Used if the issuer relies on another Authorisation Server. The Authorisation Server's issuer identifier, which is a URL that uses the "https" scheme and has no query or fragment components. Authorisation Server metadata is published at a location that is ".well-known" according to RFC 5785 [RFC5785].

If this element is omitted, the entity providing the Credential Issuer is also acting as AS, i.e. the Credential Issuer's identifier is used as the OAuth Issuer value to obtain the Authorisation Server metadata as per [RFC8414].

credential_endpoint URLrequired

REQUIRED. URL of the Credential Issuer's Credential Endpoint. This URL MUST use the https scheme and MAY contain port, path and query parameter components.

deferred_credential_endpoint URLrequired

REQUIRED. URL of the Credential Issuer's Deferred Credential Endpoint. This URL MUST use the https scheme and MAY contain port, path and query parameter components.

credentials_supported object[]required
REQUIRED. A JSON array containing a list of JSON objects, each of them representing metadata about a separate credential type that the Credential Issuer can issue.
Array [
format stringrequired
Possible values: [jwt_vc, jwt_vc_json]
A JSON string identifying the format of this credential, e.g. jwt_vc or ldp_vc. Depending on the format value, the Supported Credentials Object contains further elements defining the type and (optionally) particular claims the credential may contain, and information how to display the credential. Appendix E defines Credential Format Profiles introduced by this specification.
MUST be "jwt_vc" or "jwt_vc_json"
trust_framework objectrequired
REQUIRED: A JSON object with information about the supported trust frameworks. The 'name' property must uniquely define the trust framework.
'name' claim MUST be 'ebsi'
name Unique Trust Framework namerequired
type Credential typerequired
uri URIrequired
Link to the Verifiable Accreditation based on which the VC is issued
display object[]
OPTIONAL. An array of objects, where each object contains display properties of a Credential Issuer for a certain language. Below is a non-exhaustive list of valid parameters that MAY be included:
Array [
name string
OPTIONAL. String value of a display name for the Credential Issuer.
locale string
OPTIONAL. String value that identifies the language of this object represented as a language tag taken from values defined in BCP47 [RFC5646]. There MUST be only one object with the same language identifier
]
]

ebsiAuthoriseAndAccredit

Profile: EBSI Authorise and Accredit

{
  "authorization_server": "https://conformance-test.ebsi.eu/conformance/v3/auth-mock",
  "credential_issuer": "https://conformance-test.ebsi.eu/conformance/v3/issuer-mock",
  "credential_endpoint": "https://conformance-test.ebsi.eu/conformance/v3/issuer-mock/credential",
  "deferred_credential_endpoint": "https://conformance-test.ebsi.eu/conformance/v3/issuer-mock/credential_deferred",
  "credentials_supported": [
    {
      "format": "jwt_vc",
      "types": [
        "VerifiableCredential",
        "VerifiableAttestation",
        "VerifiableAuthorisationToOnboard"
      ],
      "trust_framework": {
        "name": "ebsi",
        "type": "Accreditation",
        "uri": "TIR link towards accreditation"
      },
      "display": [
        {
          "name": "Verifiable Authorisation to onboard",
          "locale": "en-GB"
        }
      ]
    },
    {
      "format": "jwt_vc",
      "types": [
        "VerifiableCredential",
        "VerifiableAttestation",
        "VerifiableAccreditation",
        "VerifiableAccreditationToAttest"
      ],
      "trust_framework": {
        "name": "ebsi",
        "type": "Accreditation",
        "uri": "TIR link towards accreditation"
      },
      "display": [
        {
          "name": "Verifiable Accreditation to attest",
          "locale": "en-GB"
        }
      ]
    }
  ]
}

500

Internal Server Error

application/json

Schema

Schema

type uri

Default value: about:blank

An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.

title string

A short summary of the problem type.

status int32

Possible values: >= 400 and <= 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example

{
  "type": "about:blank",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "Connection timeout\n"
}

Loading...