NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #2667 most downloaded on crates.io
OpenID Connect library
Latest stable
4.1.0
Last release 21 days ago
31 Oct 2026
Release timing varies
gaps range from 8 days to 1.3 years
Most releases are documented
notes for 26 of 29 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
51 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
This release increases the Minimum Supported Rust Version (MSRV) of this crate to 1.88.
This release increases the Minimum Supported Rust Version (MSRV) of this crate to 1.88.
into_secret on secret types by @nhaef in (#223)CoreAuthErrorResponseType by @adamgreg (#248)p256 and p384 to 0.14 to fix RUSTSEC-2026-0387. This adds a dependency on getrandom 0.4, which by default breaks compilation on wasm32-unknown-unknown and wasm64-unknown-unknown targets.itertools to 0.14 and base64 to 0.22 by @davidbarsky (#225)wasm_js feature on getrandom 0.4 to keep backward compatibility for WASM builds (see above)curve25519-dalek to 5.0Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/4.0.1...4.1.0
Fix hashing for algorithms utilizing SHA512
Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/4.0.0...4.0.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Refer to the Upgrade Guide for tips on how to upgrade from 3.x.
Refer to the Upgrade Guide for tips on how to upgrade from 3.x.
#[skip_serializing_none] (025889ebbf2161adfd76614570283af787026e2f)oauth2 to 5.0.0 (dbb3f5c4c24a0ca893bdd7d6b49ab71790304f82)Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/4.0.0-rc.1...4.0.0
oauth2 to 5.0.0-alpha.4 (19043b103b74f38137d2c0b563eadd4165d2f827)oauth2 to 5.0.0-alpha.3 along with http, reqwest, and base64 (7efc8943a8f699aff2db742827fc3d0fc2b3f34d)nightly feature (c67ffe94af24b65dbb596a68b6623baecf080eb8)oauth2 to 5.0.0-alpha.2 (fd404985ef6c8e546f951191f4e1bc791615f5ca)jwk-alg Cargo feature (73ee82f4243ef6e0e52896b97081c9b7b7226fa4)From<> for unwrapping newtypesEq for types that already derive PartialEq (898ead2e849f9fd7b3afc506d0763d3c9000a6f7)#[skip_serializing_none] (025889ebbf2161adfd76614570283af787026e2f)CoreJsonCurveType (#182)impl Future instead of Pin<Box<dyn Future>> (#158)oauth2 (1c9f77071dd29d8039e65cfeac4345584fdad56b)oauth2 to 5.0.0 (dbb3f5c4c24a0ca893bdd7d6b49ab71790304f82)JsonCurveType trait (ffde16ad678a8a1e2fda7ccd1d87e12eb4ccfee3)Display output of ClientRegistrationError (3a801c9666589450322b710ca2f38f2f99fb24f2)Cargo.toml (06e9d6cd0218a9350252f8a6a6163b16cd142f60Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/3.5.0...4.0.0
This is the first release candidate for the 4.0 major version. No further breaking changes are expected until the next major version.
This is the first release candidate for the 4.0 major version. No further breaking changes are expected until the next major version.
Refer to the Upgrade Guide for tips on how to upgrade from 3.x.
CoreJsonCurveType (#182)oauth2 to 5.0.0-rc.1Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/4.0.0-alpha.2...4.0.0-rc.1
Return impl Future instead of Pin >
impl Future instead of Pin<Box<dyn Future>> (#158)Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/4.0.0-alpha.1...4.0.0-alpha.2
This is an API-unstable release intended for gathering feedback about breaking API changes in 4.0. It should be safe to use in applications, but furth
This is an API-unstable release intended for gathering feedback about breaking API changes in 4.0. It should be safe to use in applications, but further breaking API changes MAY occur before stabilizing the API for the 4.0.0 release.
Refer to the Upgrade Guide for tips on how to upgrade from 3.x.
oauth2 to 5.0.0-alpha.4 (19043b103b74f38137d2c0b563eadd4165d2f827)oauth2 to 5.0.0-alpha.3 along with http, reqwest, and base64 (7efc8943a8f699aff2db742827fc3d0fc2b3f34d)nightly feature (c67ffe94af24b65dbb596a68b6623baecf080eb8)oauth2 to 5.0.0-alpha.2 (fd404985ef6c8e546f951191f4e1bc791615f5ca)jwk-alg Cargo feature (73ee82f4243ef6e0e52896b97081c9b7b7226fa4)From<> for unwrapping newtypesEq for types that already derive PartialEq (898ead2e849f9fd7b3afc506d0763d3c9000a6f7)oauth2 (1c9f77071dd29d8039e65cfeac4345584fdad56b)JsonCurveType trait (ffde16ad678a8a1e2fda7ccd1d87e12eb4ccfee3)Display output of ClientRegistrationError (3a801c9666589450322b710ca2f38f2f99fb24f2)Cargo.toml (06e9d6cd0218a9350252f8a6a6163b16cd142f60Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/3.5.0...4.0.0-alpha.1
Add UserInfoRequest::set_response_type by @FabianLars in https://github.com/ramosbugs/openidconnect-rs/pull/146
UserInfoRequest::set_response_type by @FabianLars in https://github.com/ramosbugs/openidconnect-rs/pull/146#[non_exhaustive] from LogoutProviderMetadata (#150)Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/3.4.0...3.5.0
This change is gated by a non-default jwk-alg feature flag, which was added to avoid introducing breaking changes. During a future major version, this…
alg field into account during key selection (#131). This change is gated by a non-default jwk-alg feature flag, which was added to avoid introducing breaking changes. During a future major version, this feature flag will be removed and the functionality will be included unconditionally.Full Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/3.3.1...3.4.0
Enable chrono wasmbind feature to fix panic in WASM environments
wasmbind feature to fix panic in WASM environments (#127)This release increases the Minimum Supported Rust Version (MSRV) of this crate to 1.65.
This release increases the Minimum Supported Rust Version (MSRV) of this crate to 1.65.
birthdate claim (#119). This crate supports a typo'ed birthday claim, which continues to work as before. In addition, it now supports the standardized birthdate claim.rsa, p256, p384, serde_with, and url dependencies to their latest versions (#117)Eq trait on structs and enums already implementing PartialEq to address Clippy lintFull Changelog: https://github.com/ramosbugs/openidconnect-rs/compare/3.2.0...3.3.0
Add support for OAuth 2.0 Device Authorization Grant, along with an example of how to use this flow with Okta (#114). This feature updates the minimum
oauth2 crate version to 4.4.1.cargo doc warnings and rustdoc linksExport PostLogoutRedirectUrl and LogoutHint
PostLogoutRedirectUrl and LogoutHintAdd support for OpenID Connect RP-Initiated Logout (#112).
Add support for OpenID Connect RP-Initiated Logout (#112).
Special thanks to @jsimonrichard for contributing this feature!
Changes that break compatibility with Rust releases older than 6 months will no longer be considered SemVer breaking changes and will not result in a…
🚀 WASM is now supported! 🚀
Don't set empty JWK signing algorithms in Client::new() (#104). This fixes a bug introduced in 3.0.0-alpha.1/2.5.0 (#87) that caused clients constructed via Client::new() not to allow any signature algorithms for ID tokens and user info JWTs unless they manually set the allowed algorithms on the IdTokenVerifier. This patch restores the original behavior of defaulting to accepting only RS256 for clients constructed via Client::new(), as indicated in the spec.
Clients constructed via Client::from_provider_metadata() will continue to receive the signing algorithms specified in the provider metadata during OpenID Connect Discovery (as introduced in 3.0.0-alpha.1/2.5.0 via #87).
AuthorizationRequest::add_scopes (#105)'static bound from ProviderMetadata::discover_async (#107)Replace ring with RustCrypto crates (#96). This change increases the minimum supported Rust version (MSRV) to 1.57 and adds support for WASM targets.
Special thanks to @sbihel for contributing this change!
Establish new MSRV policy: this crate will maintain a policy of supporting Rust releases going back at least 6 months. Changes that break compatibility with Rust releases older than 6 months will no longer be considered SemVer breaking changes and will not result in a new major version number for this crate (f3dedb3c3e74802cdf0c20d7d87ce35ffa846eb1).
CoreRsaPrivateSigningKey Send and Sync (bc09d22afc140e1d2d6caf8756dda4a17cc991fa).Changes that break compatibility with Rust releases older than 6 months will no longer be considered SemVer breaking changes and will not result in a…
Replace ring with RustCrypto crates (#96). This change increases the minimum supported Rust version (MSRV) to 1.57 and adds support for WASM targets.
Special thanks to @sbihel for contributing this change!
Establish new MSRV policy: this crate will maintain a policy of supporting Rust releases going back at least 6 months. Changes that break compatibility with Rust releases older than 6 months will no longer be considered SemVer breaking changes and will not result in a new major version number for this crate (f3dedb3c3e74802cdf0c20d7d87ce35ffa846eb1).
CoreRsaPrivateSigningKey Send and Sync (bc09d22afc140e1d2d6caf8756dda4a17cc991fa).Don't set empty JWK signing algorithms in Client::new() (#104). This fixes a bug introduced in 2.5.0 (#87) that caused clients constructed via Client:
Don't set empty JWK signing algorithms in Client::new() (#104). This fixes a bug introduced in 2.5.0 (#87) that caused clients constructed via Client::new() not to allow any signature algorithms for ID tokens and user info JWTs unless they manually set the allowed algorithms on the IdTokenVerifier. This patch restores the original behavior of defaulting to accepting only RS256 for clients constructed via Client::new(), as indicated in the spec.
Clients constructed via Client::from_provider_metadata() will continue to receive the signing algorithms specified in the provider metadata during OpenID Connect Discovery (as introduced in 2.5.0 via #87).
Ignore unrecognized signature algorithms, encryption algorithms, and public keys when parsing provider metadata and JWK sets (#99).
Ignore unrecognized signature algorithms, encryption algorithms, and public keys when parsing provider metadata and JWK sets (#99).
Previously, this crate would return a deserialization error if it encountered any unrecognized signature/encryption algorithms or public keys in the ProviderMetadata and JsonWebKeySet. This release changes the behavior to instead ignore these unexpected values, with the aim of improving compatibility with OIDC providers that support other algorithms but don't necessarily use them to sign JWTs. The OIDC spec allows for new algorithms and key types to be used, so these OIDC providers are fully compliant with the spec.
Propagate signature algorithms from OIDC discovery to token verifier (#87). Previously, these had to be configured manually when instantiating the token verifier.
serde_plain instead of the oauth2 crate's variant_name helper to convert algorithm names and other values to strings. This should ensure compatibility with arbitrary Serialize implementations for these types.ring with subtle in preparation for removing ring entirely in 3.0 (#89).Add CoreJsonWebKeyUse::Other variant to avoid JWK deserialization errors when unsupported keys are present in a provider's JWK set
CoreJsonWebKeyUse::Other variant to avoid JWK deserialization errors when unsupported keys are present in a provider's JWK set (c25eb06ba7e64e14cb94d34a564d77a4ff4e9d1b)accept-string-booleans Cargo feature flag to interoperate with non-RFC-compliant Apple OAuth (#84)CoreRsaPrivateSigningKey implement Send (#93)Only use HTTP Basic auth with a client secret (see ramosbugs/oauth2-rs#176)
Bump itertools, serde-value, and various dev dependencies. Remove untrusted crate as a dependency.
oauth2 dependency to 4.2itertools, serde-value, and various dev dependencies. Remove untrusted crate as a dependency. (#73)Add new_insecure_without_verification() to IdTokenVerifier
new_insecure_without_verification() to IdTokenVerifier (#61)ClientRegistrationResponse fields (#66)Add optional feature to accept RFC 3339 timestamps, for compatibility with Auth0
FromStr for IdToken (#59)Support JWKs with leading zeroes in their RSA modulus (n) and public exponent (e) values
n) and public exponent (e) values (#53)Update rand and base64 dependencies to their latest versions
chrono's oldtime feature flagAdd add_scopes convenience methods to request objects
add_scopes convenience methods to request objects (https://github.com/ramosbugs/oauth2-rs/pull/138)set_redirect_uri method to CodeTokenRequest (https://github.com/ramosbugs/oauth2-rs/pull/144)Client::disable_openid_scope method (#45)Fix panic in AuthorizationRequest::url when using the implicit or hybrid flows
AuthorizationRequest::url when using the implicit or hybrid flowsNothing published for this version
Disable deprecated OpenID Connect conformance tests.
oauth2 dependency to stable 4.0 release.reqwest to 0.11 and rename feature flag to reqwest. This upgrades tokio to 1.0 and removes support for both the reqwest-010 and reqwest-09 feature flags.futures 0.1 and remove the futures-01 and futures-03 feature flags; only async/await and futures 0.3 are now supported (without requiring any feature flags).Async* traits and move the request_async methods to the underlying *Request structsset_redirect_url to set_redirect_uri (see #39 for context).http 0.1 to 0.2.std::error::Error instead of failure::Fail.serde_path_to_error::Error<serde_json::Error>> in several error types to make JSON deserialization errors easier to diagnose.#[non_exhaustive] attribute to AuthType to support non-breaking additions in the future.Client::user_info fail fast with a new ConfigurationError enum when the relevant OAuth2 endpoint hasn't been configured from the OpenID Connect Discovery metadata. Previously, an error would not be returned until a call to request/request_async.reqwest client use rustls-tls by default instead of native TLS. This behavior can be overridden using the native-tls feature flag.Add rustls-tls (default) and native-tls feature flags for use with reqwest. Previously, enabling the reqwest feature flag would always use rustls. The
rustls-tls (default) and native-tls feature flags for use with reqwest. Previously, enabling the reqwest feature flag would always use rustls. The default behavior is unchanged, but users that disable the default features and wish to continue using rustls may wish to add the rustls-tls feature flag to their Cargo.toml.serde_path_to_error::Error<serde_json::Error>> instead of a serde_json::Error to improve the diagnosability of JSON deserialization errors in the following enum variants:
DiscoveryError::ParseRequestTokenError::ParseUserInfoError::Parseregistration::ClientRegistrationError::ParseRaise minimum supported Rust version (MSRV) to 1.45
set_redirect_url to set_redirect_uri (see #39 for context).reqwest to 0.11 and rename feature flag from reqwest-010 to reqwest. This upgrades tokio to 1.0.#[non_exhaustive] attribute to AuthType to support non-breaking additions in the futureClient::user_info fail fast with a new ConfigurationError enum when the relevant OAuth2 endpoint hasn't been configured from the OpenID Connect Discovery metadata. Previously, an error would not be returned until a call to request/request_async.Add support for OAuth 2.0 Token Revocation (RFC 7009).
Special thanks to @ximon18 for contributing this feature.
Add support for OAuth 2.0 Token Introspection (RFC 7662).
Special thanks to @jeroenvervaeke for contributing this feature to the oauth2 crate and to @ximon18 for porting it to this crate.
extra_fields() getter to StandardTokenIntrospectionResponseBump minimum supported Rust version (MSRV) to 1.42
ring >= 0.16.16Disable deprecated OpenID Connect conformance tests
reqwest 0.9 (previously enabled via the reqwest-09 feature flag); only the (default) reqwest-010 feature flag is now supportedhttp 0.1 to 0.2futures 0.1 and remove the futures-01 and futures-03 feature flags; only async/await is now supported (without requiring any feature flags)Async* traits and move the request_async methods to the underlying *Request structsstd::error::Error instead of failure::FailSend and Sync bounds to verification functions to enable sharing across threadsNOTE: These changes track the unstable 4.x release for the oauth2 crate.
Fix Rust 1.41 build (the 1.1.0 release used the matches! macro that was not introduced until 1.42)
matches! macro that was not introduced until 1.42)Add support for ES256/ES384 JWT signatures
ring >= 0.16.16Replace references to old master branch with main
oauth2 version pin to 3.0master branch with mainNothing published for this version
Fix UserInfo response handling when Content-Type includes a charset
ring to 0.16retry crate only a dev dependencyhyper dev dependencyapplication/jwk-set+json Content-Type in JWKS responseClient::exchange_password methodRc to Arc to improve async/thread supportrand, itertools, and base64 dependenciesAuthorizationRequest::set_redirect_url method- Re-export oauth2::{http, url}
oauth2::{http, url}…Rust version to 1.40 but should reduce future breaking changes related to enums
RefreshTokenFields and related type parameters (unnecessary since 9152d3f4d5859d224923943ae2ac6b7da7f8a850)Extension variant or #[non_exhaustive] to all exported enums; this raises the minimum supported Rust version to 1.40 but should reduce future breaking changes related to enumsoauth2 3.0.0-alpha.9, which includes reqwest 0.10 when the reqwest-010 feature flag is enabledCoreAuthErrorResponseType enumAdd a None enum variant to CoreClientAuthMethod. This variant is not mentioned in the `token_endpoint_auth_methods_supported` definition, but it is me
None enum variant to CoreClientAuthMethod. This variant is not mentioned in the token_endpoint_auth_methods_supported definition, but it is mentioned in the Core spec cited by the former. At least one major OIDC provider uses this variant.3.0.0-alpha.8 of the oauth2 crate to avoid accidentally depending on request 0.10, which the crate does not yet support.Add support for async/await and pin to oauth2 3.0.0-alpha.7. Added new docs describing the various HTTP client interfaces. Special thanks to @Folyd fo
oauth2 3.0.0-alpha.7. Added new docs describing the various HTTP client interfaces. Special thanks to @Folyd for contributing this support.CoreAuthenticationFlow by default since type_alias_enum_variants is stable. Effectively sets the minimum supported Rust version to 1.37.0.IdTokenClaims and UserInfoClaimsImpl that caused standard claims to be exposed to the deserializer for AC (additional claims). When using AC types that capture all of the remaining claims, this could lead to duplicate keys after re-serializing the claims.Have EndUserPictureUrl, EndUserProfileUrl, and EndUserWebsiteUrl wrap a String instead of a Url
EndUserPictureUrl, EndUserProfileUrl, and EndUserWebsiteUrl wrap a String instead of a UrlMake IdTokenFields::id_token and TokenResponse::id_token return an Option.
IdTokenFields::id_token and TokenResponse::id_token return an Option.RefreshIdTokenFields now that it's identical to IdTokenFields.NonceVerifier.DateTime arguments and return types owned values instead of references.enable_openid_scope and disable_openid_scope methods to Client.require_audience_match and require_issuer_match methods to IdTokenVerifier.aud claim (defaults to empty Vec). Note that ID token validation will still fail unless require_audience_match is used to disable audience validation.IdToken::into_claims method.UserInfoClaims::standard_claims method.Bump oauth2 dependency to 3.0.0-alpha.6, which changes the constructors for the URL-based NewTypes (AuthUrl, TokenUrl, RedirectUrl). See that crate's
oauth2 dependency to 3.0.0-alpha.6, which changes the constructors for the URL-based NewTypes (AuthUrl, TokenUrl, RedirectUrl). See that crate's release notes for details. This update also renames reqwest::async_http_client to reqwest::future_http_client and each request_async method to request_future.Bump oauth2 dependency to 3.0.0-alpha.4, which also bumps url to 2.1. This change introduces curl and reqwest feature flags, with reqwest enabled by d
oauth2 dependency to 3.0.0-alpha.4, which also bumps url to 2.1.
This change introduces curl and reqwest feature flags, with reqwest
enabled by default.Make CoreGenderClaim a string NewType instead of an enum
CoreGenderClaim a string NewType instead of an enumSerialize timestamps as integers
Have LocalizedClaim::get take Option<&LanguageTag> instead of &Option
LocalizedClaim::get take Option<&LanguageTag> instead of &Option<LanguageTag>- export LocalizedClaim type
LocalizedClaim typeNothing published for this version
Nothing published for this version
One column per quarter.