Code works on localhost, but not when promoted to a dev server, gettign auth SDK error

Questions API
1

Using basic login with okta , using okta vue 2 js in a vue app.

On local host, with .net web api running on local host, I get no errors and it all works fine

Then I Promote the api and the Vue app (both secured by okta) to our devserver, when I login, it gets to the success promise

Uncaught (in promise) r {name: ‘AuthSdkError’, message: ‘The app should not attempt to call getToken on cal…in process. Use parseFromUrl() to receive tokens.’, errorCode: ‘INTERNAL’, errorSummary: ‘The app should not attempt to call getToken on cal…in process. Use parseFromUrl() to receive tokens.’, errorLink: ‘INTERNAL’, …}errorCauses: errorCode: "INTERNAL"errorId: "INTERNAL"errorLink: "INTERNAL"errorSummary: "The app should not attempt to call getToken on callback. Authorize flow is already in process. Use parseFromUrl() to receive tokens."message: "The app should not attempt to call getToken on callback. Authorize flow is already in process. Use parseFromUrl() to receive tokens."name: “AuthSdkError”[[Prototype]]: Error
at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:4056)
at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)
at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:11626)
at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)
at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:6207)
at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)
at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:16577)
at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)
at eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:498)
at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:508)stack: “Error\n at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:4056)\n at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)\n at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:11626)\n at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)\n at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:6207)\n at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)\n at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:16577)\n at t (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:141)\n at eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:498)\n at Object.eval (webpack:///./node_modules/@okta/okta-vue/bundles/okta-vue.umd.js?:26:508)”[[Prototype]]: Object

What’s weird is that call stack looks like all okta code, none of our code.

So I Search for a call to GetToken in our code and it’s not called anywhere, it is called in the Okta code.

2

How is your widget configured? It seems like there is authorization_code flow in flight, which conflicts with getToken call. Would be interesting to see how you configured your login page

3

It’s the okta hosted widget with just an HTML skin over it, using the tools i the admin console to add the html

4

I’m running okta -vue 2, was a breaking change made on the back end that could cause this?

Here is the html we put in with the standard widget

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

<meta name="viewport" content="width=device-width, initial-scale=1.0" />

<meta name="robots" content="none" />



<title>{{pageTitle}}</title>

{{{SignInWidgetResources}}}

<link rel="preconnect" href="https://fonts.googleapis.com">

        <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>

        <link href="https://fonts.googleapis.com/css2?family=Source+Sans+Pro&display=swap" rel="stylesheet">

<style>

  body {

    font-family: 'Source Sans Pro', sans-serif;

   

  }

  p {text-align: center;}

</style>

You have accessed a United States Department of Labor, Job Corps Computer System,

which may be used only for official Government business by authorized personnel.

Use of the system without authorization or for purposes for which authorization

has not been granted is a violation of Federal law and can be punished with fines

or imprisonment (Public Law 99-474).

All information on this computer system may be intercepted, recorded, read, copied,

and disclosed by and to authorized personnel for official purposes, including criminal investigations.

Access or use of this computer system by any person whether authorized or unauthorized

constitutes consent to these terms. Logging in signifies that the user has

read, understands, and will abide by the Job Corps Network Rules of Behavior.

<div class="login-bg-image" style="background-image: {{bgImageUrl}}"></div>

<div id="okta-login-container"></div>



<!--

    "OktaUtil" defines a global OktaUtil object

    that contains methods used to complete the Okta login flow.

 -->

{{{OktaUtil}}}



<script type="text/javascript">

    // "config" object contains default widget configuration

    // with any custom overrides defined in your admin settings.

    var config = OktaUtil.getSignInWidgetConfig();



    // Render the Okta Sign-In Widget

    var oktaSignIn = new OktaSignIn(config);

    oktaSignIn.renderEl({ el: '#okta-login-container' },

        OktaUtil.completeLogin,

        function(error) {

            // Logs errors that occur when configuring the widget.

            // Remove or replace this with your own custom error handler.

            console.log(error.message, error);

        }

    );

</script>