Profile support in metadata

[OIDF-automation]

Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/2004

Original Reporter: tlodderstedt

Implementers have requested to add metadata claims to allow a wallet to determine the profiles a certain issuer supports (such as DDIP or HAIP).

[OIDF-automation]

Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda

makes sense. is there a need to make changes beyond metadata, because the wallet will have to communicate which profile it chose to use? though probably not.

also would this also impact presentation, not just issuance?

[OIDF-automation]

Imported from AB/Connect bitbucket - Original Commenter: ThierryThevenet

Yes, that is our use case.
The point is that must of the features of a profile should be discoverable in the metada but :

• some ecosystems (issuer/verifiers) use older release of the specs or does not respect exactly the standards
• some features are beyond the scope of the protocol, i am thinking about Trust management for instance
  So a “profile” attribute would be great in some specific cases….

[OIDF-automation]

Imported from AB/Connect bitbucket - Original Commenter: ThierryThevenet

the custom scheme could also be used

‌

[Sakurann]

believe we can add this in a non-breaking manner post 1.0 if we need to