We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, I think I found an issue. It's not a biggie but I am posting it here for tracking purpose.
Here's the scenario
FooCredential
"offeredCredentialConfigurations": { "FooCredential": { "proof_types_supported": { "jwt": { "proof_signing_alg_values_supported": [ "EdDSA", "ES256", "ES256K" ] } }, "format": "jwt_vc_json", "credential_definition": { "type": [ "VerifiableCredential", "FooCredential" ] } } },
using code such as
export const fooCredential = { id: 'FooCredential', format: OpenId4VciCredentialFormatProfile.JwtVcJson, types: ['VerifiableCredential', ServiceCredentialTypes.Foo], } satisfies OpenId4VciCredentialSupportedWithId; async function createOffer(...) { .... return await this.#issuanceAgent.createCredentialOffer([ fooCredential.id, ]); }
When holder requests credential, actually issue him different credential BarCredential
BarCredential
{ '@context': [ 'https://www.w3.org/2018/credentials/v1' ], type: [ 'VerifiableCredential', 'BarCredential' ], credentialSubject: { number: '123456789', id: 'did:key:z6MkuAXvSM64j7nAFo6mqzFAeg4HLz7rPXsqeGtHTWuaEW9M' }, issuanceDate: '2024-10-01T08:31:19Z', expirationDate: undefined, issuer: 'did:key:z6MktiQQEqm2yapXBDt1WEVB3dqgvyzi96FuFANYmrgTrKV9', id: undefined }
export const barCredential = { id: 'BarCredential', format: OpenId4VciCredentialFormatProfile.JwtVcJson, types: ['VerifiableCredential', ServiceCredentialTypes.Bar], } satisfies OpenId4VciCredentialSupportedWithId; requestToCred: OpenId4VciCredentialRequestToCredentialMapper = async ({ issuanceSession, holderBinding, }): Promise<OpenId4VciSignCredential> => { .... { credentialSupportedId: barCredential.id, format: ClaimFormat.JwtVc, credential: new W3cCredential({ type: barCredential.types, issuer: new W3cIssuer({ id: issuerDidKey.did, }), credentialSubject: new W3cCredentialSubject({ id: parseDid(holderBinding.didUrl).did, claims, }), issuanceDate: w3cDate(Date.now()), }), verificationMethod: `${issuerDidKey.did}#${issuerDidKey.key.fingerprint}`, }; }
eg. simply issuing BarCredential instead of "promised" FooCredential
I guess I would expect Holder to error out upon receiving the credential, but right now the credential is succesfuly stored.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, I think I found an issue. It's not a biggie but I am posting it here for tracking purpose.
Here's the scenario
FooCredential
(the following is fragment of resolved credential offer)using code such as
When holder requests credential, actually issue him different credential
BarCredential
using code such as
eg. simply issuing
BarCredential
instead of "promised"FooCredential
I guess I would expect Holder to error out upon receiving the credential, but right now the credential is succesfuly stored.
The text was updated successfully, but these errors were encountered: