Okta OIDC callbacks hanging in the UI when not authorized

[xeivieni]

Describe the bug When using the UI to login with oidc auth method (using okta as provider) if the user is not allowed to log in (or is there is a configuration issue) the UI hangs forever with login button spinning.

On the other hand, when trying to do the same thing through the vault cli it clearly fails showing an error message, eg :

Error authenticating: Error making API request.

URL: GET https://vault.xx.com/v1/auth/okta-oidc/oidc/callback?client_nonce=XXX&code=XXX&id_token=&state=XXX
Code: 400. Errors:

* error validating claims: claim "name" does not match any associated bound claim values

Expected behavior An error should also be displayed in the UI in case of an error

Environment:

• Vault Server Version (retrieve with vault status): 1.12.0
• Vault CLI Version (retrieve with vault version): 1.11.4
• Server Operating System/Architecture: kubernetes using official helm chart

[EvertonSA]

This is not only Okta specific, seems to happen on all oidc providers. I tested with gitlab and github and the UI hangs in case of error.