Error while processing route: vault.index in WebUI #7385
Comments
|
We'll fix the bug that you're hitting, but it seems to be from an unexpected localStorage state. Try opening the browser dev tools and in the console type |
|
That fixed it. Turn's out also it wasn't Chrome specific. My Firefox eventually ran into the same problem. |
|
Hmm that's bizarre - what auth method are you using? It'd be good to chase down the root cause as well as fixing this check. |
|
i am hitting this on occasion as well. |
|
Can confirm the same. Site is blank when I login using OIDC but it works fine in other browsers and incognito. Finding the site here and clearing it seems to work chrome://settings/siteData Google Chrome is up to date Vault is 1.2.2 |
Primarily using userpass. |
|
Duplicate of #7349 blank page after Renew Token with OIDC auth. renew-self responds policies: null
@meirish I drilled this down to an API call which returns policies: null. see linked issue for details. @upodroid can you reproduce it using the steps in #7349 ? @craigday can you reproduce it in an incognito window with userpass login? I did not see the issue with userpass login. |
|
I was simply testing using the github auth backend, but the issue happened after adding a new kv2 secrets engine through the cli. That made the UI suddenly go blank and display the error in the console that was reported in the initial issue. |
|
I have the same problem. localStorage.clear() fix worked, but quite annoying. Pls fix. |
|
I am having the same issue. Using the authentication method "Username". Using version: Vault 1.3.0. If I login with incognito mode in chrome (or clear my storage) then it is fine I am able to login. Using windows 10 and Chrome: 79.0.3945.117 The error log from chrome: |
|
Pls give a higher priority to this issue. Thanks a lot! |
|
Yes please fix! |
|
Hi @meirish |
|
I am doing a triage on this issue from the backend's side. Are there other requests that's causing this issue aside from renew-self (and possibly renew)? |
|
We saw this issue in the UI for our staging environment (v1.4.0-beta). For us it happens on the landing page, prior to any login attempt or any other interaction. |
|
We've been able to reproduce this issue and have a fix in the works on the backend side that should resolve this. The issue stems from the fact that, unlike a login request, the policies field returned from a renewal request does not contain the full set of policies, so there are cases where that field might be nil even though the token does indeed contain other attached policies (such as the default or identity-derived policies). It's worth noting that this is a payload response inconsistency, and does not affect the actual policies that are attached to the token. Due to possible scope of impact, we will need more time to test and to discuss the changes internally. We have this scheduled for the 1.5 release, and will provide further updates if things change. |
Getting the following Javascript error while trying to access the WebUI in Chrome Version 76.0.3809.100 on OSX.
Vault Version: 1.2.2
Error while processing route: vault.index Cannot read property 'includes' of null TypeError: Cannot read property 'includes' of null
Console image attached. I have restarted the browser and performed a hard reload/clear of the cache.
Seems to be working fine in Firefox.
The text was updated successfully, but these errors were encountered: