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

Introduce jose crate which is a thin wrapper around the josekit open source crate #74

Merged
merged 6 commits into from
Apr 11, 2024

Conversation

KendallWeihe
Copy link
Contributor

Introduce jose crate such that we don't leak abstractions, and in the event we need to swap underlying implementations, then it's contained to a single crate and not everywhere

We're using josekit as the underlying JOSE library https://crates.io/crates/josekit

I still need to update the credentials crate, but will do so in a subsequent PR because this one is too unweildy already

@@ -20,3 +20,6 @@ pub trait KeyStore: Send + Sync {
private_key: Arc<dyn PrivateKey>,
) -> Result<(), KeyStoreError>;
}

// todo I don't think we should enable private keys to ever leave the KeyStore,
// so `get` doesn't make sense and `insert` should be replaced with a `generate()` method
Copy link
Contributor Author

Choose a reason for hiding this comment

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

important IMO but will be for later

@KendallWeihe KendallWeihe merged commit 1ee3082 into kendall/main Apr 11, 2024
@KendallWeihe KendallWeihe deleted the kendall/jose branch April 11, 2024 18:50
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