[Openid-specs-ab] Issue #1639: Enable automatic update of Verifiable Credentials (openid/connect)

[Daniel McGrogan]

New issue 1639: Enable automatic update of Verifiable Credentials
https://bitbucket.org/openid/connect/issues/1639/enable-automatic-update-of-verifiable

Daniel McGrogan:

A definition of how the wallet should automatically get refreshed or updated Verifiable Credentials would be useful for many business processes. For example an office access credentials which need to be refreshed on a daily basis. In this case we don't want the end user to need to scan the same QR code every day or multiple QR codes multiple times a day. Once the relationship has been established the wallet would continue to receive the latest VC without demanding any interaction.

This could be accomplished by pushing the credentials from the issuer to the wallet or having the wallet call directly to the issuer for the latest credential. They are not mutually exclusive options. The former can provide lower latency horizontally scalable solution as well as better user experience and the latter drives no additional availability requirements to the wallet client.

This handling has already been defined in other [openid.net](http://openid.net) specs, see: [https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1\_0.html#rfc.section.5](https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.5)

An inclusion like of the ‘Poll, Ping, and Push Modes’ style addition would unlock rich issuance use cases.