Skip to content

Commit

Permalink
Applied Guiseppe's suggestion
Browse files Browse the repository at this point in the history
Co-authored-by: Giuseppe De Marco <demarcog83@gmail.com>
  • Loading branch information
selfissued and peppelinux authored Sep 21, 2024
1 parent fc7a0a4 commit f741930
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion openid-federation-wallet-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -455,7 +455,7 @@ The process of trust establishment in federated environments is illustrated in t

Wallets SHOULD periodically check their Wallet Providers' compliance through the federation's trust infrastructure. This involves retrieving the Wallet Provider's Entity Configuration and verifying its Trust Chain up to a recognized Trust Anchor, ensuring that the Wallet Provider has not been revoked within the federation. Wallets SHOULD remain neutral in attesting to the reliability of their Wallet Providers for the End-User, thereby protecting the End-User against any malevolent behavior by the Wallet Provider.

The Wallet Provider’s Entity Configuration provides essential information, including its roles within the federation, policies it adheres to, and cryptographic keys for secure communication. In the example represented in the sequence diagram below, the Wallet Instance uses the Federation API to discover and collect all the Wallet Providers enabled within the federation.
The Wallet Provider’s Entity Configuration provides essential information, including its roles within the federation, policies it adheres to, and cryptographic keys for secure communication. The Wallet Instance SHOULD use the Federation API to periodically reestablish trust with its Wallet Provider.

The process to discover the trust with a Wallet Provider is equivalent to the one used for discoving the trust with a Credential Issuer, as described in the dedicated section below.

Expand Down

0 comments on commit f741930

Please sign in to comment.