Releases: panva/openid-client
Releases · panva/openid-client
v2.2.0
- added support for RFC8414 - OAuth 2.0 Authorization Server Metadata discovery
encrypted_id_token
property added to TokenSet instances with the value of the encrypted ID Token value before its decryption
v2.1.1
v2.1.0
v2.0.4
v2.0.3
v2.0.2
v2.0.1
- fixed
client_secret_basic
requiring the username and password tokens to bex-www-form-urlencoded
according to https://tools.ietf.org/html/rfc6749#section-2.3.1- NOTE: Although technically a fix, this is a breaking change when used with providers that also
don't currently follow the standard. A proper way of submitting client_id and client_secret usingclient_secret_basic
isAuthorization: base64(formEncode(client_id):formEncode(client_secret))
. If your client_id and client_secret does contain special characters that need encoding this does not affect you. If it does, try usingclient_secret_post
instead.
- NOTE: Although technically a fix, this is a breaking change when used with providers that also
v2.0.0
- dropped support for Node.js v4.x due to its End-of-Life on 2018-04-30
- removed deprecated
client#grantAuth
- removed deprecated way of passing keystore directly to
Client#register
- removed support for passing client to
OpenIDConnectStrategy
as single argument, usenew Strategy({ client })
instead ofnew Strategy(client)
. - fixed a bug requiring nonce to be passed for
response_type=none