We should say more about user_hint

Issue #1978 resolved
Michael Jones created an issue

https://openid.bitbucket.io/connect/openid-4-verifiable-credential-issuance-1_0.html#name-oauth-20 defines user_hint in this way:

  • user_hint: OPTIONAL. JSON String containing an opaque user hint the Wallet MAY use in subsequent callbacks to optimize the user's experience. RECOMMENDED in Dynamic Credential Request.

I was left puzzled how developers are expected to use user_hint. What kinds of information is it expected to convey and how do we envision that information being used?

I believe that this note also indicates that we need to say more:

Note to the editors: need to sort out Credential Issuer's client_id with Wallet and potentially add example with wallet_issuer and user_hint

Comments (1)

  1. Log in to comment