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
With the release of the first draft of the TR 119 479-2, which outlines a process for implementing a pricing policy within the EAAs, it would be valuable to explore the integration of credential management for these types within the IT Wallet, as outlined in the standard: https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=73779
The text was updated successfully, but these errors were encountered:
Could we leverage this feature to enable other use cases, such as allowing a credential issuer to restrict the use of its credentials with specific relying parties (RPs)?
The value of this feature lies in granting credential issuers complete control over their credentials. In other words, credentials become a type of protected resource where user consent alone is insufficient. Credential issuers thus become integral to the authorization process.
We completely agree on the vision, the Issuers in this scenario could grant access to the credentials only if there is an agreement with the specific RP.
In general our vision is that the RP should check on the Attribute Rulebook and ask a presentation of a credential that suits their needs or on which they agree to comply with the pricing policy.
With the release of the first draft of the TR 119 479-2, which outlines a process for implementing a pricing policy within the EAAs, it would be valuable to explore the integration of credential management for these types within the IT Wallet, as outlined in the standard: https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=73779
The text was updated successfully, but these errors were encountered: