search

decentralized-identity / jwt-vc-presentation-profile

https://identity.foundation/jwt-vc-presentation-profile/
Apache License 2.0
15 stars 15 forks source link

Why is the custom protocol `openid-vc://` instead of `openid://` #33

Closed brianorwhatever closed 2 years ago

brianorwhatever commented 2 years ago

SIOPv2 declares the custom scheme as openid: however this profile declares it as openid-vc:

tplooker commented 2 years ago

Hey there is still active conversation on this topic see here

Sakurann commented 2 years ago

SIOP v2 reserves the usage of openid:// only with the specific set of wallet's metadata. so implementations that use metadata diverging with static metadata tied to openid:// need to use other custom URL scheme. It could be anything. this document just picked openid-vc:

Sakurann commented 2 years ago

@tplooker the conversation in the bitbucket you are pointing to is the custom URL scheme used in issuance when there is no scheme defined elsewhere or pre-registered. issuance profiles like this one can define other custom url schemes.

dtmcg commented 2 years ago

@brianorwhatever &| @tplooker anything further to add otherwise we can close the issue

brianorwhatever commented 2 years ago

Discussed on the 07-20-22 call at around 43 min mark (https://us02web.zoom.us/rec/play/B_hNAzYDF-e1OMpC4nTtQ3Q82-fBqPq6aa3pV-wYlJAOLiqZJgBYEdqS0JNjQ-FyO3naTTPkP3lKeI_8.8gi_jsa9J5aZ0td3?continueMode=true&_x_zm_rtaid=z0N3jp3pTsuIsCe81aL-Lw.1658352572828.66bc836390b98bc7e6c1346ad60d5684&_x_zm_rhtaid=936) @Sakurann explained it well, thank you

"The openid:// scheme in the oidc spec maps to the static metadata set out in the spec, this profile has custom metadata so that is what is being mapped to the openid-vc:// protocol here"