You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ jsonwebtoken = { version = "10", features = ["aws_lc_rs"] }
15
15
serde = {version = "1.0", features = ["derive"] }
16
16
```
17
17
18
-
Two crypto backends are available via features, `aws_lc_rs` and `rust_crypto`, exactly one of which must be enabled.
18
+
Two crypto backends are available via features, `aws_lc_rs` and `rust_crypto`, at most one of which must be enabled. If you select neither feature, you need to provide your own `CryptoProvider`.
19
+
See e.g. [arckoor/jsonwebtoken-botan](https://github.com/arckoor/jsonwebtoken-botan) for an example of how to implement a `CryptoProvider`.
19
20
20
21
The minimum required Rust version (MSRV) is specified in the `rust-version` field in this project's [Cargo.toml](Cargo.toml).
Could not automatically determine the process-level CryptoProvider from jsonwebtoken crate features.
122
+
Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the 'rust_crypto' and 'aws_lc_rs' features is enabled.
123
+
See the documentation of the CryptoProvider type for more information.
124
+
"###);
125
+
let _ = provider.install_default();
126
+
Self::get_default().unwrap()
127
+
}
128
+
129
+
/// Determine a `CryptoProvider` based on crate features.
0 commit comments