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

for single-use algorithm, document whether the issuer and holder algorithms may be different #78

Open
dwaite opened this issue Jul 13, 2023 · 4 comments
Assignees
Labels
JPA JSON Proof Algorithms
Milestone

Comments

@dwaite
Copy link
Collaborator

dwaite commented Jul 13, 2023

From @OR13, https://mailarchive.ietf.org/arch/msg/jose/GkL3I9hEoKjaIDCgno_rYqQsSP0/ :

An example with a mixed algorithm for issue and holder would be nice here,
or a comment about it being forbidden... for example issuer signing with
ES256 and holder presenting with EdDSA.

@dwaite dwaite added the JPA JSON Proof Algorithms label Jul 13, 2023
@selfissued
Copy link
Collaborator

Clearly the issuer and holder algorithms have to be able to be different. I'll review the specs with this in mind.

@dwaite dwaite self-assigned this Jan 5, 2024
@dwaite
Copy link
Collaborator Author

dwaite commented Feb 17, 2024

I believe this work has been done, @selfissued are you ok with this being closed?

@selfissued
Copy link
Collaborator

Let's consider this together with #57. On the surface of it, it seems that we have to to address that one to address this one.

@dwaite
Copy link
Collaborator Author

dwaite commented Feb 27, 2024

I do not think this is the same as #57 / #59 . We just need to make this clear for algorithms in general

@dwaite dwaite added this to the draft-3 milestone Feb 27, 2024
@dwaite dwaite modified the milestones: draft-3, draft-4 Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
JPA JSON Proof Algorithms
Projects
None yet
Development

No branches or pull requests

2 participants