Even if the application works somehow, it's a terribly confusing example, since the code is obviously incorrect.
On top of that, even the field naming in that new RequestorBuilder call is very weird: schema.uri is set to credentialType (which is an array), but issuance[0].manifest is set to an URL. Something is definitely amiss here.
For some reason the example app is written in plain JS, not TS. So, there's no type verification.
Looks like the type for RequestorBuilder constructor call https://github.com/Azure-Samples/active-directory-verifiable-credentials/blob/main/issuer/app.js#L86 does not match at all to the type in the SDK: https://github.com/microsoft/VerifiableCredentials-Verification-SDK-Typescript/blob/cadc9c787315662d561a32e7c83c22c2983f9f95/lib/api_oidc_request/RequestorBuilder.ts
When I've debugged the application and checked how the payload is populated https://github.com/microsoft/VerifiableCredentials-Verification-SDK-Typescript/blob/cadc9c787315662d561a32e7c83c22c2983f9f95/lib/api_oidc_request/Requestor.ts#L49 - sure enough, it was full of
undefined
s.Even if the application works somehow, it's a terribly confusing example, since the code is obviously incorrect.
On top of that, even the field naming in that
new RequestorBuilder
call is very weird:schema.uri
is set tocredentialType
(which is an array), butissuance[0].manifest
is set to an URL. Something is definitely amiss here.