: Could not load PKCE codeVerifier from storage

Questions
1

Hello,

We are getting this intermittent issue of the user staring at a blank screen, when its console log tells him the following errror -
okta-auth-js.umd.js:2 Uncaught (in promise) AuthSdkError: Could not load PKCE codeVerifier from storage. This may indicate the auth flow has already completed or multiple auth flows are executing concurrently.
at e.value (okta-auth-js.umd.js:2:77845)
at e.value (okta-auth-js.umd.js:2:76971)
at okta-auth-js.umd.js:2:219673
at r (okta-auth-js.umd.js:2:258765)
at Generator._invoke (okta-auth-js.umd.js:2:258553)
at Generator.next (okta-auth-js.umd.js:2:259190)
at r (okta-auth-js.umd.js:2:265082)
at a (okta-auth-js.umd.js:2:265287)
at okta-auth-js.umd.js:2:265346
at new Promise ()

Outr application is using
“@okta/okta-auth-js”: “6.6.2”,
“angular”: “1.7.7”

Our application challenges user with token, when the user visits the URL, however, if the system remains active for more than 8 hours, the token expires. Sometimes, our users do not turn off the computer, and in such cases, when they revisit our website, whose token has expired, they are presented with this error.

The error goes away, if the user hits refresh button, or types in the website name again. We are of opinion that this might be a library related issue, because none of our application code gets invoked or none of our console logs get printed in such scenarios.

Please provide suggestions if you have encountered similar scenario.

thanks,
Swapnil.

2

There are a few historical conversations about this error on Github that I would recommend looking through: React LoginCallback Component: "AuthSdkError: Could not load PKCE codeVerifier from storage. This may indicate the auth flow has already completed or multiple auth flows are executing concurrently. · Issue #898 · okta/okta-oidc-js · GitHub

Are you only seeing this error occur when the user attempts to come back to the application after their token’s have expired? Is autoRenew set to true (this is the default value) for OktaAuth?

3

Hi, we’re also facing the same issue. We have a React SPA using Okta auth js for redirect auth and getting the same error intermittently. we’re using Okta-auth-js 7.0.1 and okta-react 6.7.0. We’re using sessionStorage for tokens and we didn’t set autoRenew, which means is should be default to true. The error happens on chrome. We’ve gone through the referenced Github issue but in that issue the error happens on MS Edge and also with older versions of Okta auth js. Could you provide other pointers on what could be the issue? thanks.

4

Can you ensure that the /authorize call is getting initiated by the SDK so that the SDK is the one generating/storing a code_verifier and then providing the code_challenge in the authorize request?

5

We’re using the Okta auth js to interact with Okta, we don’t have other code to generate the code_verifier or call Okta /authorize endpoint. thanks.