Releases: okta/okta-auth-js
@okta/[email protected]
@okta/[email protected]
Features
New option cookies
allows overriding default secure
and sameSite
values.
Breaking Changes
-
#308 - Removed
jquery
andreqwest
httpRequesters -
#309 - Removed
Q
library, now using standard Promise. IE11 will require a polyfill for thePromise
object. Use ofPromise.prototype.finally
requires Node > 10.3 for server-side use. -
#310 - New behavior for signOut()
postLogoutRedirectUri
will default towindow.location.origin
- signOut() will revoke access token and perform redirect by default. Fallback to XHR closeSession() if no idToken.
- New method closeSession() for XHR signout without redirect or reload.
- New method revokeAccessToken()
-
#311 - parseFromUrl() now returns tokens in an object hash (instead of array). The
state
parameter (passed to authorize request) is also returned. -
#313 - An HTTPS origin will be enforced unless running on
http://localhost
orcookies.secure
is set tofalse
-
#316 - Option
issuer
is required. Optionurl
has been deprecated and is no longer used. -
#317 -
pkce
option is nowtrue
by default.grantType
option is removed. -
#320 -
getWithRedirect
,getWithPopup
, andgetWithoutPrompt
previously took 2 sets of option objects as parameters, a set of "oauthOptions" and additional options. These methods now take a single options object which can hold all available options. Passing a second options object will cause an exception to be thrown. -
- Default responseType when using implicit flow is now
['token', 'id_token']
. - When both access token and id token are returned, the id token's
at_hash
claim will be validated against the access token
- Default responseType when using implicit flow is now
-
#325 - Previously, the default
responseMode
for PKCE was"fragment"
. It is now"query"
. Unless explicitly specified using theresponseMode
option, theresponse_mode
parameter is no longer passed bytoken.getWithRedirect
to the/authorize
endpoint. Theresponse_mode
will be set by the backend according to the OpenID specification. Implicit flow will use"fragment"
and PKCE will use"query"
. If previous behavior is desired, PKCE can set theresponseMode
option to"fragment"
. -
#329 - Fix internal fetch implementation.
responseText
will always be a string, regardless of headers or response type. If a JSON object was returned, the object will be returned asresponseJSON
andresponseType
will be set to "json". Invalid/malformed JSON server response will no longer throw a raw TypeError but will return a well structured error response which includes thestatus
code returned from the server.
Other
-
#306 - Now using babel for ES5 compatibility. All polyfills have been removed.
-
#312 - Added an E2E test for server-side authentication (node module, not webpack).
@okta/[email protected]
Bug Fixes
-#338 - (Fix for Chrome 80) Setting 'Secure' on cookies if running on HTTPS. Setting 'SameSite=Lax' on cookies if running on HTTP. TokenManager (if using cookie storage) will retain previous behavior, setting 'SameSite=Lax' in all cases unless tokenManager.secure
is set to true
via config.
@okta/[email protected]
Bug Fixes
- #334 - Setting 'SameSite=none' for all cookies (Fix for iFrame)
2.13.0
2.12.1
2.12.0
2.11.2
2.11.1
2.11.0
2.11.0
Features
- #288 - New options for
signOut
:- Can provide a post-logout redirect URI.
- Can revoke access token
Bug Fixes
- #288 - calling
signOut
will clear the TokenManager. - #284 -
isPKCESupported
will return false ifTextEncoder
is not available (IE Edge).
Other
- #284 - better error messages when attempting to use PKCE in an unsupported browser configuration.