Module crypto 

Process-wide jsonwebtoken crypto provider selection.

jsonwebtoken infers its provider from its own two backend features, and with both on it cannot: it falls back to a provider that panics on first use. Cargo features being additive, that combination arrives on its own. Either this crate’s rust_crypto and aws_lc_rs are both enabled (two dependents asking for different backends, or --all-features, which is what docs.rs and cargo-semver-checks use), or one of ours is enabled while another crate in the graph turns on the other jsonwebtoken feature directly. The second case looks single-backend from here, so the provider is installed explicitly whichever backend this crate compiled with.

Functions

install_default_crypto_provider

Select the jsonwebtoken crypto provider for this process.