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

[Interoperability][JAR] Authorization Request Object requirements for interoperability #317

Closed
4 tasks
Zicchio opened this issue Jan 8, 2025 · 1 comment · Fixed by #325
Closed
4 tasks
Assignees
Milestone

Comments

@Zicchio
Copy link
Collaborator

Zicchio commented Jan 8, 2025

The interoperability requirements for the Authorization Request (which, in the case of the cross device flow, is the content of the QR code) has some differences with the current implementation. If we want to comply with potential, then we should find a way to satisfy those requirements.

Currently, the differences in the request object compared to the current implementation are:

  • the request object jwt should include an aud claim with value equal to "https://self-issued.me/v2"
  • client_id_scheme is omitted as no trust framework is used in potential
  • presentation_definition is inserted directly in the request object as no trust framework is used in potential
  • response_mode should be direct_post (this is related to [Interoperability] Support for unencrypted direct_post authz response mode  #310) as no trust framework is used in protential

I leave myself the option to edit the message is order to include further requirements relating the request object if or when they are observed.

@Zicchio Zicchio self-assigned this Jan 8, 2025
@peppelinux peppelinux added this to the 0.9.1 milestone Jan 10, 2025
@peppelinux peppelinux moved this from Todo to In Progress in EUDI WALLET IT Python Jan 10, 2025
@Zicchio
Copy link
Collaborator Author

Zicchio commented Jan 10, 2025

Part of this issue includes #290

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

Successfully merging a pull request may close this issue.

2 participants