Sign in not authorized

[NatalieDinh]

Describe the bug?

When attemping to sign in, I receive a Error: Sign in not authorized with error code -1000.

My organization does not have any MFAs enabled, and we are sure that the credentials are accurate as we are able to get a access token through the OIDC debugger.

What is expected to happen?

I should be able to sign in and receive an access token in return.

What is the actual behavior?

I receive an Error: Sign in not authorized, -1000 error and no further action occurs. There is also no further description as to what the specific issue is.

Reproduction Steps?

I replaced the samples.config.js file with

export default {
  oidc: {
    redirectUri: REDIRECT_URI,
    endSessionRedirectUri: END_REDIRECT_URI,
    clientId: CLIENT_ID,
    discoveryUri: DISC_URL,
    scopes: ['openid', 'profile', 'offline_access'],
  },
};

and then run the application per usual, using the credentials of an OKTA user I've created using the OKTA dashboard that has access to the application.

Additional Information?

No response

SDK Version

~2.3.0

Build Information

No response