I think it's safe to say we can conform this exemplar to assume a KCC is the expected credential format, let's update the exemplar to make that assumption throughout
I know we'll need to update the seed-offerings script to define the required claims to be compatible with the KCC schema, but there may be other places throughout the exemplar where this can be assumed
I think it's safe to say we can conform this exemplar to assume a KCC is the expected credential format, let's update the exemplar to make that assumption throughout
KCC json schema here https://github.com/TBD54566975/known-customer-credential/blob/main/kcc-schema.json
I know we'll need to update the seed-offerings script to define the required claims to be compatible with the KCC schema, but there may be other places throughout the exemplar where this can be assumed