Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Pricing Policy for EAA within the IT Wallet #591

Open
19Simone98 opened this issue Mar 11, 2025 · 2 comments
Open

Support for Pricing Policy for EAA within the IT Wallet #591

19Simone98 opened this issue Mar 11, 2025 · 2 comments
Milestone

Comments

@19Simone98
Copy link

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

@peppelinux
Copy link
Member

@19Simone98 thank you for this feature proposal

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.

@luigicastaldo
Copy link

@peppelinux thank you for your feedback.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants