Package-level declarations
Types
OID4VCI: The request parameter authorization_details
defined in Section 2 of (RFC9396) MUST be used to convey the details about the Credentials the Wallet wants to obtain. This specification introduces a new authorization details type openid_credential
and defines the following parameters to be used with this authorization details type.
Server implementation to issue credentials using OID4VCI.
OID4VCI: Object indicating to the Wallet the Grant Types the Credential Issuer's Authorization Server is prepared to process for this Credential Offer. Every grant is represented by a name/value pair. The name is the Grant Type identifier; the value is an object that contains parameters either determining the way the Wallet MUST use the particular grant and/or parameters the Wallet MUST send with the respective request(s).
OID4VCI: The Credential Issuer sends Credential Offer using an HTTP GET request or an HTTP redirect to the Wallet's Credential Offer Endpoint defined in Section 11.1.The Credential Offer object, which is a JSON-encoded object with the Credential Offer parameters, can be sent by value or by reference.
OID4VCI: W3C VC: To express the specifics about the claim, the most deeply nested value MAY be an object that includes the following parameters defined by this specification (other parameters MAY also be used).
OID4VCI: OPTIONAL. Object with information about the logo of the Credential.
OID4VCI: OPTIONAL. Array of objects, where each object contains the display properties of the supported Credential for a certain language.
To be serialized into /.well-known/openid-credential-issuer
Used by CredentialIssuer to obtain user data when issuing credentials using OID4VCI.
This implements RFC8414 All descriptions taken from section 2.
Interface used in SimpleAuthorizationService to actually load user data, converting it into OidcUserInfo.
Source: https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html OpenID for Verifiable Credential Issuance Published: 3 February 2023
Adapter implementation to convert userInfo obtained from an OAuth2AuthorizationServer into credentials needed by IssuerCredentialDataProvider.
Holds a deserialized OidcUserInfo as well as a JsonObject with other properties, that could not been parsed.
Simple authorization server implementation, to be used for CredentialIssuer, when issuing credentials directly from a local dataProvider.
OID4VCI: Object that describes specifics of the Credential that the Credential Issuer supports issuance of. This object contains a list of name/value pairs, where each name is a unique identifier of the supported Credential being described. This identifier is used in the Credential Offer to communicate to the Wallet which Credential is being offered.
OID4VCI: W3C VC: REQUIRED. Object containing the detailed description of the Credential type. It consists of at least the following two parameters: type,
credentialSubject`.
OID4VP: An object containing a list of key value pairs, where the key is a string identifying a Credential format supported by the Wallet. Valid Credential format identifier values are defined in Annex E of OpenID.VCI. Other values may be used when defined in the profiles of this specification.
Client service to retrieve credentials using OpenID for Verifiable Credential Issuance. Implemented from Draft openid-4-verifiable-credential-issuance-1_0-11
, 2023-02-03.
Functions
Reverse functionality of encodeToCredentialIdentifier
Empty strings can not be decoded by decodeURLQueryComponent, so we'll need to filter it.