ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself).You can achieve the same result by closing it manually close will close this PR and stop Dependabot recreating it.reopen will reopen this PR if it is closed.cancel merge will cancel a previously requested merge and block automerging.squash and merge will squash and merge this PR after your CI passes on it.merge will merge this PR after your CI passes on it.recreate will recreate this PR, overwriting any edits that have been made to it.You can trigger Dependabot actions by commenting on this PR: You can also trigger a rebase manually by commenting rebase. Additional commits viewable in compare viewĭependabot will resolve any conflicts with this PR as long as you don't alter it yourself.77e2a58 Release version 1.14.4 of the npm package.2ad9e82 Carry over Host header on relative redirects ( #172).2e1eaf0 Keep Authorization header on subdomain redirects.86f7572 Fix: clear internal timer on request abort to avoid leakage.d01ab7a Release version 1.14.5 of the npm package.6f5029a Release version 1.14.6 of the npm package.8b347cb Drop Cookie header across domains.2ede36d Release version 1.14.7 of the npm package.Hoping to generate some discussion around this RFC and see if this leads us to a Revocation Notification v1.1 or v2.0.Ĭc follow-redirects from 1.14.1 to 1.14.7. It also seems to break up the clean separation between business logic and the DIDComm messaging layer, requiring the business logic driver to be aware of message details in order to correlate the notification with a credential.Īs an alternative, the idea of including credential identifiers as an attachment to the revocation notification was raised, allowing the definition of what attributes are expected for each credential system to be externalized from the revocation notification RFC. However, this requires both sides of the exchange to map from thread ID to credential system specific identifier for the credential. The thread ID provides a simple, already present, credential system independent identifier. The thread ID is used as a consistent identifier for both the issuer and holder of a credential.
During the ACA-PUG meeting today, we had a brief discussion about usage of the thread ID as the identifier for a credential used within the notification.
0 kommentar(er)
