You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`Requested response mode ${responseMode} is not supported by the issuer according to its configuration ${JSON.stringify(responseModeSupported)}`
87
100
);
88
-
thrownewError(`No response mode support the type '${credentialType}'`);
101
+
thrownewError(`No response mode support the type '${credentialTypes}'`);
89
102
}
90
103
91
-
returnresponseMode;
104
+
returnresponseMode!;
92
105
};
93
106
94
107
/**
95
108
* WARNING: This function must be called after {@link evaluateIssuerTrust} and {@link startFlow}. The next steam is {@link compeUserAuthorizationWithQueryMode} or {@link compeUserAuthorizationWithFormPostJwtMode}
109
+
*
96
110
* Creates and sends a PAR request to the /as/par endpoint of the authorization server.
97
111
* This starts the authentication flow to obtain an access token.
98
-
* This token enables the Wallet Instance to request a digital credential from the Credential Endpoint of the Credential Issuer.
112
+
* This token enables the Wallet Instance to request a digital credential from the Credential Endpoint of the Credential Issuer; when multiple credential types are passed,
113
+
* it is possible to use the same access token for the issuance of all requested credentials.
99
114
* This is an HTTP POST request containing the Wallet Instance identifier (client id), the code challenge and challenge method as specified by PKCE according to RFC 9126
100
115
* along with the WTE and its proof of possession (WTE-PoP).
101
116
* Additionally, it includes a request object, which is a signed JWT encapsulating the type of digital credential requested (authorization_details),
* to the Wallet Instance's Token Endpoint to obtain the Access Token, and the redirectUri of the Wallet Instance where the Authorization Response
106
121
* should be delivered. The redirect is achived by using a custom URL scheme that the Wallet Instance is registered to handle.
107
122
* @param issuerConf The issuer configuration
108
-
* @paramcredentialType The type of the credential to be requested returned by {@link selectCredentialDefinition}
123
+
* @paramcredentialTypes The type of the credential(s) to be requested
109
124
* @param ctx The context object containing the Wallet Instance's cryptographic context, the Wallet Instance's attestation, the redirect URI and the fetch implementation
110
-
* @returns The URI to which the end user should be redirected to start the authentication flow, along with the client id, the code verifier and the credential definition
125
+
* @returns The URI to which the end user should be redirected to start the authentication flow, along with the client id, the code verifier and the credential definition(s)
0 commit comments