Releases: badgateway/oauth2-client
Release list
v2.0.14
v2.0.13
Version 2 stable release!
Version 2 is a complete rewrite of this library that broadens the scope of to be a fully-featured general OAuth2 client. This package has been renamed from fetch-mw-oauth2 to @badgateway/oauth2-client.
The setup of this library has changed a lot, so if you are upgrading from 1.x.x or 0.x.x, you will have to change how you're setting up the OAuth2 setup. Take a look at the instructions in the readme to see how.
New features in v2
- A general OAuth2 client library, with functions such as
authorizationCode,clientCredentials, allowing you to directly access these features. - PKCE support for
authorization_code. - Support for OAuth2 Token Introspection (RFC7662).
- OAuth2 endpoint discovery via the Server metadata document (RFC8414).
- Now uses Node 18's native
fetchimplementation. It's still possible to polyfill this withnode-fetch, but this is not set up by default anymore. There's documentation on setting up the polyfill in the readme.
New since the last alpha release
- Renamed this package from
fetch-mw-oauth2to@badgateway/oauth2-client. - #59: Scope support for
authorization_codeflow.
v2.0.12
Version 2 stable release!
Version 2 is a complete rewrite of this library that broadens the scope of to be a fully-featured general OAuth2 client. This package has been renamed from fetch-mw-oauth2 to @badgateway/oauth2-client.
The setup of this library has changed a lot, so if you are upgrading from 1.x.x or 0.x.x, you will have to change how you're setting up the OAuth2 setup. Take a look at the instructions in the readme to see how.
New features in v2
- A general OAuth2 client library, with functions such as
authorizationCode,clientCredentials, allowing you to directly access these features. - PKCE support for
authorization_code. - Support for OAuth2 Token Introspection (RFC7662).
- OAuth2 endpoint discovery via the Server metadata document (RFC8414).
- Now uses Node 18's native
fetchimplementation. It's still possible to polyfill this withnode-fetch, but this is not set up by default anymore. There's documentation on setting up the polyfill in the readme.
New since the last alpha release
- Renamed this package from
fetch-mw-oauth2to@badgateway/oauth2-client. - #59: Scope support for
authorization_codeflow.
v1.0.1
v2.0.10
Fetch-mw-oauth2 v2 alpha
This is an alpha version of the upcoming v2. Version 2 is a complete rewrite of this library that broadens the scope of to be a fully-featured general OAuth2 client.
The fetch wrapper is still available, but it's just one of its features. The setup of this library has changed a lot, so if you are upgrading from 1.x.x or 0.x.x, you will have to change how you're setting up the OAuth2 setup. Take a look at the instructions in the readme to see how.
New features in v2
- A general OAuth2 client library, with functions such as
authorizationCode,clientCredentials, allowing you to directly access these features. - PKCE support for
authorization_code. - Support for OAuth2 Token Introspection (RFC7662).
- OAuth2 endpoint discovery via the Server metadata document (RFC8414).
- Now uses Node 18's native
fetchimplementation. It's still possible to polyfill this withnode-fetch, but this is not set up by default anymore. There's documentation on setting up the polyfill in the readme.
v1.0.0
v0.7.0
- Ensure that only 1 refresh operation will happen in parallel. If there are
multiple things triggering the refresh, all will wait for the first one
to finish. - Automatically schedule a refresh operation 1 minute before the access token
expires, if the expiry time is known. - BC Break: If a token is known when setting up OAuth2, this now needs to be
passed as the second argument. The old behavior still works but will emit
a warning, and will be removed in a future release. - 'OAuth2Token' type is now exported.