[Openid-specs-ab] Issue #2147: Handling credential issuer's that go offline (openid/connect)

[Andres Olave]

New issue 2147: Handling credential issuer's that go offline
https://bitbucket.org/openid/connect/issues/2147/handling-credential-issuers-that-go

Andres Olave:

I raised this issue during IIW and I didnt feel i got a complete answer

I think that the credential use case requires adjustment of the spec to deal with credential issuer's that goes offline due to termination as an issuer, no longer being a going concern due to liquidation or similar event, rebranding, etc. In most of these cases the issued credentials are still valid.

If the Issuer goes offline the Entity Statement will no longer be available under the .well-known location. The spec says that trust can still be established by using the TA/Intermediary fetch and resolve endpoints. 

Therefore i am looking for feedback on the following  3 suggestions:

1. There should be additional exceptions added to 9 "Obtaining Federation Entity Configuration Information" for this case.
2. Non-normative statements addressing the need for some federations to backup the Entity Configurations of their entities. I think that that the credential could look to refer to the federation fetch endpoint to use if the .well-known endpoint is not available. This seems related to \`authority\_hints\` from an Entity Configuration, or \`trust\_anchor\_id\` of the OP uses when communicating to a client or resource server.
3. Addition of claims to the Entity Statement that track historical trust in an entity or creation of a profile that refers to new claims that track trust establishment and termination over time such as \`trust\_validity: \[\{established\_at: 1234832941, terminated\_at: 1235833132\}, \{established\_at: 1236001946\}\]\`

thanks!

‌