Update dependency @okta/okta-auth-js to v7 #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^6.7.6
->^7.0.0
Release Notes
okta/okta-auth-js (@okta/okta-auth-js)
v7.8.1
Bug Fix
jsonpath-plus
modulev7.8.0
Features
v7.7.1
extraParams
passed to/authorize
and include them during token refresh7.7.0
Features
Fixes
7.6.0
Features
getOrRenewAccessToken
revokeSessions
param forOktaPassword
authenticator (can be used inreset-authenticator
remediation)RenewOnTabActivation
Bug Fix
issuer
"-admin" validation to.okta
domain7.5.1
Bug Fix
OktaAuthOptions
now requiresissuer
aud
array7.5.0
Bug Fix
ReEnrollAuthenticatorWarning
Other
broadcast-channel
version to5.3.0
HttpRequestClient
andIdentifyValues
7.4.3
Bug Fix
launch-authenticator
rememdiation on safari7.4.2
Bug Fix
7.4.1
Bug Fix
7.4.0
Features
#1440 Fixes type of
tokenManager.getSync
#1439
.signOut
improvementspostLogoutRedirectUri: null
to.signOut
now omits the param from/logout
call and will observe the behavior of/logout
state
is now returned as a query param to thepostLogoutRedirectUri
when.signOut
falls back to.closeSession
#1412
authClient.token.introspect
tokens
param torenewTokens
Fixes
relatesTo
in IDX responseOther
customLabel
toInput
type7.3.1
Fixes
7.3.0
Features
react-native
topackage.json
closeSession()
andsignOut()
to booleanFixes
LeaderElectionService
start7.2.0
Features
endpoints.authorize.enrollAuthenticator
. AddshandleRedirect
and deprecateshandleLoginRedirect
.Fixes
AutoRenewService
start7.1.1
Fixes
currentAuthenticatorEnrollment
toIdxContext
7.1.0
Features
/authorize
and/interact
endpointsOther
7.0.2
Fixes
uiDisplay
property toIdxContext
typedeviceKnown
property toIdxAuthenticator
typeidentify
remediation7.0.1
Fixes
7.0.0
Breaking Changes
options
field fromNextStep
of IDX transaction6.9
nonce
param toidx.interact
(andidx.start
)6.8.1
Fixes
broadcast-channel
to 4.17, removingmicrotime
sub dependency6.8.0
Other
./polyfill
in package.jsonisAbsoluteUrl
6.7.7
6.7.6
Fixes
6.7.5
Fixes
default
export under./browser
to support[email protected]+
6.7.4
Fixes
select-enrollment-channel
remediation now accepts protocol defined inputs, as well as conveniencesbroadcast-channel
version at4.13.0
,4.14.0
requires node 14+ (This fix has been applied to 6.5.4 and up)6.7.3
options.step
is available6.7.2
Fixes
6.7.1
Fixes
#1245 IDX GenericRemediator patches (beta):
IdxAuthenticator
IdxTransaction.availableSteps
#1247 - Fixes OV enrollment flow issue in authentication flow.
6.7.0
Features
SyncStorageService
usingbroadcast-channel
instead of usingStorageEvent
. SupportslocalStorage
andcookie
storage.LeaderElectionService
as separate serviceChannel is closed
while stopping leader election6.6.3
6.6.2
Fixes
6.6.1
Fixes
broadcast-channel
6.6.0
Features
oktaAuth.start
/oktaAuth.stop
now return aPromise
, ensures services have started/stopped before resolvingFixes
undefined
error when use GenericRemediator (beta)6.5.4
broadcast-channel
at4.13.0
to prevent node minimum version regressions6.5.3
relatesTo
type fromNextStep
6.5.2
Fixes
6.5.1
Fixes
canRemediate
logic in GenericRemediator (beta) to handle nested fieldscanRemediate
logic in GenericRemediator (beta) to handleoptions
fieldsOther
Input
type inidx
module6.5.0
Features
maxAge
param in interaction code flow. This parameter can be passed in from either SDK level options oridx.interact
options.options
field ininputs
scope, and deprecated top leveloptions
fromnextStep
field of the response (removal will happen in the next major version).Fixes
input
type indicator's field name forusername
andauthenticator
. Before the indicator was named askey
, now it's fixed totype
to follow input metadata with all other inputs.6.4.5
Fixes
stepUp
on returnedIdxTransaction
6.4.4
Fixes
credentials
object6.4.3
Fixes
credentials.answer
ApiError
,responseType
,responseMode
6.4.2
Fixes
dynamic import
transpiling issue6.4.1
Fixes
#1177 - fixes issue with repeated calls to
oktaAuth.start()
6.4
Features
requestDidSucceed
is returned onIdxTransaction
shouldProceedWithEmailAuthenticator
to disable email authenticator auto-selectionFixes
#1145
user
property now optionalkey
property#1161
Other
6.3.2
Fixes
6.3.1
Fixes
6.3.0
Features
authenticator
can be provided to IDX methods as either a string (representing the authenticator key) or an authenticator objectcredentials
object can be passed to satisfy an "identify" remediation instead ofusername
andpassword
idx.proceed
will continue without saved transaction meta if astateHandle
is availablerequestDidSucceed
which will be false if the XHR was returned with a non-2xx HTTP statusFixes
transformAuthState
. Concurrent auth state updates will now enqueue calls totransformAuthState
so that they execute sequentiallystep
option in IDX flows: it will only be used for a single remediation cycleOther
6.2.0
Features
SigninWithCredentialsOptions
andSignInOptions
to supportSP Initiated Auth
authenticator-verification-data
remediationFixes
import
syntaxFixes
state
now stored in session during verifyEmail flowOther
autoRenew
(active vs passive)isAuthenticated
to override client configurationisAuthenticated
, tokens are now read fromtokenManager
(not memory) before expiration is checked6.1.0
Features
webauthn
authenticator support in idx moduleinvokeApiMethod
method as an escape hatch to make arbitrary OKTA API requestX-Forwarded-For
,User-Agent
,X-Okta-User-Agent-Extended
andX-Device-Token
) toidx.interact
. Follow setHeaders section to add headers to http requests.Fixes
Input
type in NextStep objectSigninOptions.context
typeupdateAuthState
whenhandleLoginRedirect
failsOther
cross-fetch
to resolve security vulnerability6.0.0
Breaking Changes
UserClaims<{ groups: string[]; }>
userAgent
field from oktaAuth instanceuseMultipleCookies
from CookieStorage optionsclearTokensAfterRedirect
clearTokensBeforeRedirect
(default:false
) to remove local tokens before logout redirect happenintrospect
is renamed tointrospectAuthn
(still callable astx.introspect
)IdxFeature
enum is now defined as strings instead of numbersFeatures
recoveryToken
andactivationToken
otp
to idx pipelineexchangeCodeForTokens
. If false,interactionCode
will be returned on the transaction at the end of the flow instead oftokens
.autoRemediate
. If false, there will be no attempt to satisfy remediations even if values have been passed.saveLastResponse
. If false, IDX responses will not be cached.useInteractionCodeFlow
defaults totrue
for sample and test apps.5.11.0
5.10.1
Fixes
5.10.0
Features
clearPendingRemoveTokens
option insignOut
method. This option can be used to avoid cross tabs sign out issue with Okta's downstream client SDK'sSecureRoute
componentsecurity question
authenticator support in idx moduleFixes
token.renew()
will be emitted and containtokenKey
propertyisAuthenticated()
because of failed token renewal5.9.1
Other
type
field in package.json. As okta-auth-js includes multiple bundles (cjs, esm, umd) in the package, explicittype
field causes error for some type of bundlers. This change fixes issue with @angular/cli.5.9.0
Features
authorize
urlOther
browser
field inpackage.json
to enable bundlers to use the ES module bundle by defaultFixes
rememberMe
boolean in IDX Identify remediation adaptertype
field forInput
type in NextStep object5.8.0
Features
5.7.0
Features
setHeaders
Fixes
getWithPopup
issueauthn
related requestsgetToken
Other
SignInWithRedirectOptions
should extendTokenParams
Input
type in NextStep objectscopes
config param is anarray
5.6.0
Features
getPreviousAuthState
method toAuthStateManager
Google Authenticator
support in idx moduleOther
AuthState
interfaceBug Fixes
parseFromUrl
if can't load transaction meta5.5.0
Features
ignoreLifetime
option to disable token lifetime validationheaders
with response headers to all responsesBug Fixes
5.4.3
Bug Fixes
tokenManager
config (optionsautoRenew
,autoRemove
) inOktaAuth.isAuthenticated
.AuthTransaction
when user is not assigned.5.4.2
Bug Fixes
authStateManager.updateAuthState
during login redirect instart
method.5.4.1
5.4.0
Features
renewed
event forTokenManager.setTokens
methodcrypto
util module5.3.1
Bug Fixes
MFA_REQUIRED
status5.3.0
Features
http.setRequestHeader
Bug Fixes
state
fromtoken.parseFromUrl
Other
token.parseFromUrl
signature (adds optional parameter)5.2.3
Bug Fixes
isAuthenticated
state during active token auto renew by only checking existence of both tokens from storage5.2.2
class
keyword5.2.1
5.2.0
Features
idx.recoverPassword
- checks if flow is supportedBug Fixes
@okta/okta-idx-js
missing core-js dependency.SDK_VERSION
placeholder issueOther
tsd
from dependencies to devDependencies@okta/okta-idx-js
to 0.18.0 (replacedjsonpath
withjsonpath-plus
)5.1.1
Bug Fixes
5.1.0
Features
updateAuthState
returns a Promise.idx
module. See details in IDX README.md5.0.3
Bug Fixes
5.0.2
Bug Fixes
5.0.1
Bug Fixes
handleLoginRedirect
where a redirect could occur after an exception was thrown.4.9.2
Bug Fixes
4.9.1
Bug Fixes
handleLoginRedirect
where a redirect could occur after an exception was thrown.5.0.0
Features
cookies.sessionCookie
optionBreaking Changes
start
andstop
are added to controlOktaAuth
as a service.token.value
fieldtokenManager.expireEarlySeconds
option with the default value (30s) for non-dev environmentoriginalUri
is null.isPending
fromAuthState
Other
updateAuthState
when there are no subscribersisAuthenticated
will renew expired tokens whenautoRenew
is true4.9.0
Bug Fixes
TokenManager.renew
to renew only requested tokenFeatures
token.renewTokensWithRefresh
4.8.0
Features
Bug Fixes
Other
4.7.2
Bug Fixes
fetch
on IE Edge versions 14-17.4.7.1
Bug Fixes
StorageManagerOptions
4.7.0
Features
interaction_code
anderror=interaction_required
on redirect callbackstorageManager
andtransactionManager
Bug Fixes
Other
@babel/runtime
to dependencies list.4.6.2
Bug Fixes
fetch
on IE Edge versions 14-17.4.6.1
catch
when using refresh token originally from #5794.6.0
Features
Other
error
orerror_description
thenisLoginRedirect
will return true andparseFromUrl
will throwOAuthError
4.5.1
Bug Fixes
catch
when using refresh token4.5.0
Features
token.prepareTokenParams
token.exchangeCodeForTokens
pkce.generateVerifier
pkce.computeChallenge
and constant:
pkce.DEFAULT_CODE_CHALLENGE_METHOD
This API allows more control over the
PKCE
authorization flow and is enabled for both browser and nodeJS.4.4.0
Features
4.3.0
Features
claims
toAccessToken
4.2.0
Features
scopes
configuration option now handles 'offline_access' as an option, which will use refresh tokens IF your client app is configured to do so in the Okta settingsscopes
and wishing to add 'offline_access' should passscopes: ['openid', 'email', 'offline_access']
to their constructorrenewTokens()
will now use an XHR call to replace tokens if the app has a refresh token. This does not rely on "3rd party cookies"autoRenew
option (defaults totrue
) already callsrenewTokens()
shortly before tokens expire. TheautoRenew
feature will now automatically make use of the refresh token if presentsignOut()
now revokes the refresh token (if present) by default, which in turn will revoke all tokens minted with that refresh tokensignOut()
follow the existingrevokeAccessToken
parameter - whentrue
(the default) any refreshToken will be also be revoked, and whenfalse
, any tokens are not explicitly revoked. This parameter name becomes slightly misleading (as it controls both access AND refresh token revocation) and will change in a future version.4.1.2
Bug Fixes
VerifyRecoveryTokenOptions
4.1.1
Bug Fixes
scopes
that are set in the constructor4.1.0
Features
AuthStateManager
to evaluate and emit latest authState. Exposes new methods fromAuthStateManager
:authStateManager.getAuthState
authStateManager.updateAuthState
authStateManager.subscribe
authStateManager.unsubscribe
sdk.signInWithCredentials
sdk.signInWithRedirect
sdk.isAuthenticated
sdk.getUser
sdk.getIdToken
sdk.getAccessToken
sdk.storeTokensFromRedirect
sdk.setOriginalUri
sdk.getOriginalUri
sdk.removeOriginalUri
sdk.isLoginRedirect
sdk.handleLoginRedirect
sdk.signIn
sdk.tokenManager
:tokenManager.getTokens
tokenManager.setTokens
transformAuthState
restoreOriginalUri
autoRemove
devMode
AuthState
.hasResponseType
,isPKCE
,isAuthorizationCodeFlow
. The optionresponseType
is now accepted in the constructor.Bug Fixes
4.0.3
Bug Fixes
4.0.2
#491 Fixes issue with OAuth param cookie when using self-hosted signin widget
#489 Fixes sameSite cookie setting when running on HTTP connection
4.0.1
Bug Fixes
4.0.0
Features
tokenManager.hasExpired
to test if a token is expiredBreaking Changes
tokenManager.get
. Now they will be renewed or removed in the background. If autoRenew is true, tokens will be renewed before expiration. If autoRenew is false, tokens will be removed from storage on expiration.onSessionExpired
option has been removed. TokenManager events can be used to detect and handle token renewal errors.tokenManager.get
no longer implements autoRenew functionality (autoRenew is done by a separate process withinTokenManager
). Even withautoRenew
, it is possible that the token returned from the TokenManager may be expired, since renewal is an asynchronous process. New methodtokenManager.hasExpired
can be used to test the token and avoid this potential race condition.3.2.6
token.isLoginRedirect
issue withcode
query params in url3.2.5
#491 Fixes issue with OAuth param cookie when using self-hosted signin widget
#489 Fixes sameSite cookie setting when running on HTTP connection
3.2.4
Bug Fixes
3.2.3
Bug Fixes
3.2.2
Bug Fixes
3.2.1
Bug Fixes
sdk.fingerprint
3.2.0
Features
-#408 Provides a polyfill for IE 11+
-#410 Add
token.isLoginRedirect
function to prevent app from starting new Oauth flow while already in OAuth callback state.3.1.4
Bug Fixes
#400 Allows an accessToken to be retrieved without an idToken. Also allows retrieving "default" scopes as defined by the custom authorization server.
#402 Fixes tokenManager cookie storage size limitation issue by store tokens in separated cookies.
3.1.3
Bug Fixes
#395 Prevents concurrent use of token API methods such as
getWithoutPrompt
,getWithRedirect
orgetWithPopup
within a single running instance. These methods will be executed within a queue to ensure that they complete sequentially. This fix only affects a single instance. If there are several instances running (for example, in multiple tabs) it is still possible for token API methods to be executing concurrently.#399 Fixes an error involving PKCE flow and the signin widget.
3.1.2
token.verify
:validationParams
should be optional.3.1.1
Bug Fixes
Will reject with error if PKCE is enabled but not supported when OIDC flow is initiated. Previously this check was done in the constructor and affected non-OIDC flows
Will print a console warning and disable secure cookies if cookies.secure is enabled on an HTTP connection. Previously this would throw in the constructor.
3.1.0
Features
3.0.1
Bug Fixes
#354 - Omit cookies from API requests. Removes warning messages in latest version of Chrome.
#355 - Fix for authorization_code flow for non-SPA applications (when responseType=code and pkce=false). The code can be retrieved client-side using
parseFromUrl()
without throwing an error.3.0.0
Features
New option
cookies
allows overriding defaultsecure
andsameSite
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
#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.#321
['token', 'id_token']
.at_hash
claim will be validated against the access token#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).
2.13.2
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 totrue
via config.2.13.1
Bug Fixes
2.13.0
Features
responseMode: "query"
option for SPA apps using PKCE flow2.12.1
Bug Fixes
getWellKnown
was using base url over issuer. Method has been fixed to use issuer, if configured, and will fallback to base url2.12.0
Features
2.11.2
Features
onSessionExpired
2.11.1
Other
2.11.0
Features
signOut
:Bug Fixes
signOut
will clear the TokenManager.isPKCESupported
will return false ifTextEncoder
is not available (IE Edge).Other
2.10.1
Other
2.10.0
Features
Bug Fixes
Other
2.9.0
Features
Bug Fixes
2.7.0
Features
2.6.3
Other
grantType
has been deprecated and will be removed in 3.02.6.2
Features
pkce
Bug Fixes
(#233) The default
responseMode
was incorrectly set tofragment
instead ofquery
when theresponseType
wascode
. This regression was introduced in version2.6.0
.747216b fix build process, so that /dist/okta-auth-js.min.js is for browsers (since version 2.2.0, dist/ output was being built for node.js applications, which was not intended)
2.6.1
Features
expireEarlySeconds
Bu
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.