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

RP Solution - same device flow #74

Closed
fmarino-ipzs opened this issue Jul 19, 2023 · 1 comment · Fixed by #77
Closed

RP Solution - same device flow #74

fmarino-ipzs opened this issue Jul 19, 2023 · 1 comment · Fixed by #77
Assignees
Labels
Milestone

Comments

@fmarino-ipzs
Copy link
Collaborator

In the (Q)EAA Issance flow as defined in the PR #70, we require the Issuer to perform a PID presentation request to the Wallet Instance according to [OpenID4VP] following a same-device flow. In the current version of the IT Wallet specification we only have defined a cross-device authorization flow.

We should add technical details in the Same Device Flow Section.

@fmarino-ipzs fmarino-ipzs self-assigned this Jul 19, 2023
@peppelinux peppelinux added this to the 0.6.0 milestone Jul 20, 2023
@peppelinux peppelinux self-assigned this Jul 24, 2023
@peppelinux
Copy link
Member

I have implemented the same-device flow in the RP IAM proxy, according to OpenID4VP, here:

https://github.com/italia/eudi-wallet-it-python/blob/dev/pyeudiw/satosa/backend.py#L160

OpenID4VP says

The following non-normative example of an Authorization Request refers to the Authorization Request Object 
from above through the request_uri parameter. The Authorization Request can be displayed to 
the End-User either directly (as a link) or as a QR Code:

https://wallet.example.com?
    client_id=https%3A%2F%2Fclient.example.org%2Fcb
    &request_uri=https%3A%2F%2Fclient.example.org%2F567545564

I'll do a PR asap for enabling this in the current specs

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

Successfully merging a pull request may close this issue.

2 participants