Skip to content
This repository has been archived by the owner on Jun 21, 2024. It is now read-only.

How to use OID4VC in a Client Perspective way #9

Open
mschmidt-ffstudios opened this issue Dec 5, 2023 · 1 comment
Open

How to use OID4VC in a Client Perspective way #9

mschmidt-ffstudios opened this issue Dec 5, 2023 · 1 comment

Comments

@mschmidt-ffstudios
Copy link

Hello together,

OID4VC is as far as I know a User Based flow:

  • The entire workflow is based on user interaction and consent management
  • A User is using his mobile Wallet but for a Company an automated process (client) would do the work
  • A Client should be able to use the same Workflow with a configuration of Interaction Criteras

Is this planned to be added in OID4VC since if this is missing, a Company wallet can not directly use OID4VC
since it is only described for User flows.

If we want to enable Companies, there should be a possibility to develop an Client based Access flow or?

Greetings,
Max

@tlodderstedt
Copy link
Contributor

Hi,

OID4VC was developed with users (natural person) in mind. Most of the protocol components are dedicated to ensure the security of the interaction with the user and are not needed for clients/machines.

For the issuance, you could certainly use the credential issuance endpoint to issue credentials to machines. You would obtain the access token using other grant types, such as "client_credential" or the attestation based client attestation.

Not sure on the presentation side. Could you share your use case(s)? That would help to come up with an idea.

best regards,
Torsten.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants