Releases: okta/okta-auth-js
1.17.0
1.16.0
1.15.0
Bug fix
- Fix the token.getWithPopup doesn't work in IE10/11 when cross domains. #105
1.14.0
1.13.0
1.9.0
1.8.0
1.7.0
1.6.0
We've further expanded our OAuth 2.0 support to include Shared Authorization Servers (Beta). Now, you can pass a custom issuer, authorizeUrl or userinfoUrl to token.getWithRedirect, token.getWithoutPrompt or token.getWithPopup. We've also made it easier to validate idTokens server-side by using the okta-oauth-state and okta-oauth-nonce cookies. For additional browser-side validation of idTokens, token.verify will validate the signature in browsers that natively support cryptography (Chrome, Edge, Firefox, and Opera).
Features:
- e39e6cd - Adds Shared Authorization Server support (#47)
- 83f2675 - Adds token.verify (#49)
- 82e5a1d - Adds state and nonce cookies for server-side idToken validation (#51)
Other notable changes:
- af21c3b - Adds caching to well-known configuration requests (#48)
- 83f2675 - Deprecates idToken.verify (#49)
- 7310870 - Changes distributed filename from OktaAuth.min.js to okta-auth-js.min.js (#50)
You can get the latest release from npm.
1.5.0
We've expanded our OAuth 2.0 and OpenID Connect support. Now, you can retrieve user details with token.getUserInfo or create an authorization code for server-side flows. Additionally, the tokenManager is no longer necessary to refresh an access or ID token; token.refresh allows you to refresh the token directly.
Features:
- 1c598a6 - Added token.refresh (#39)
- e8ac02c - Added authorization code support (#40)
- a4147b3 - Added token.getUserInfo (#41)
- 28a1700 - Improved performance when refreshing tokens simultaneously (#44)
Bug fixes:
Other notable changes:
You can get the latest release from npm.