You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a proof request is received and the user does not have the credential, the wallet uses credential_support_url from OCA as the hyperlink for the "Get this credential" button. This is counter intuitive as that credential_support_url is meant to be the hyperlink to the support url (i.e. the contact us page or email) for the credential. It is meant to be accompanied by the credential_help_text (and it's text display). This is defined in the credential design guide: https://bcgov.github.io/digital-trust-toolkit/docs/resources/guides/credential-ux-guide#credential-meta-information
This is causing some confusion with people building their own OCA bundle.
Acceptance Criteria
Switch the reference from credential_support_url to issuer_url
The text was updated successfully, but these errors were encountered:
LCRB seem to have built their OCA to match how BC Wallet is currently referencing credential_support_url. i.e. their meta overlay links to the issuance page. Whereas the student card OCA is built to match the credential design guide.
Background
When a proof request is received and the user does not have the credential, the wallet uses credential_support_url from OCA as the hyperlink for the "Get this credential" button. This is counter intuitive as that credential_support_url is meant to be the hyperlink to the support url (i.e. the contact us page or email) for the credential. It is meant to be accompanied by the credential_help_text (and it's text display). This is defined in the credential design guide: https://bcgov.github.io/digital-trust-toolkit/docs/resources/guides/credential-ux-guide#credential-meta-information
This is causing some confusion with people building their own OCA bundle.
Acceptance Criteria
Switch the reference from credential_support_url to issuer_url
The text was updated successfully, but these errors were encountered: