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

Update API surface to support Kanidm KeyObjects #28

Merged
merged 3 commits into from
Apr 10, 2024

Conversation

Firstyear
Copy link
Member

This updates a large amount of the API surface to support Kanidm key objects. This also changes the way we created the key id to make it more reliable to derive for verifiers.

  • [ x ] cargo fmt has been run
  • [ x ] cargo test has been run and passes
  • [ x ] documentation has been updated with relevant examples (if relevant)

This updates a large amount of the API surface to support Kanidm
key objects. This also changes the way we created the key id to
make it more reliable to derive for verifiers.
@Firstyear Firstyear requested a review from yaleman April 9, 2024 06:52
@dmulder
Copy link
Collaborator

dmulder commented Apr 9, 2024

Will you be updating the hsm-crypto version in a different MR?

Copy link
Member

@yaleman yaleman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some clippy-isms

src/crypto/es256.rs Outdated Show resolved Hide resolved
src/crypto/x509.rs Outdated Show resolved Hide resolved
src/crypto/es256.rs Outdated Show resolved Hide resolved
@Firstyear
Copy link
Member Author

Will you be updating the hsm-crypto version in a different MR?

Good point, updated it here.

@yaleman yaleman merged commit bcee118 into main Apr 10, 2024
1 check passed
@yaleman yaleman deleted the 20240321-key-object-support branch April 10, 2024 04:04
@@ -46,7 +54,7 @@ impl JwsBuilder {
self
}

/// Set the kid
#[cfg(test)]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was here for a reason. MS requires a very specific header when sending a Windows Hello assertion.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that was my mistake :)

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

Successfully merging this pull request may close these issues.

3 participants