miagilepner

Hi @carishkaa, your staging app has permission checks disabled which would cause this behavior. Please try updating your app and setting `disable_permissions_checks: false`. I'm going to close this ticket since...

The workarounds mentioned in the thread will work for the time being. We've also added this as a feature request to our backlog. Because this issue describes a backend feature...

Thanks for reporting this. This is a good idea and we've added this as a feature request to our backlog. In the meantime, because this issue describes a backend feature...

Thanks for reporting this. This is a good idea and we've added this as a feature request to our backlog with your user stories attached. We don't yet have an...

Hi, I need a bit more information in order to try to reproduce this. Do the tokens that you're querying for have `token_policies` or `identity_policies`? And are you using namespaces...

@Plipplopplip how many policies do you have?

Hi, I can't seem to reproduce this. In order to help debug, can you please confirm: 1. What the server's cors config value is? e.g.: ``` curl \ -H "X-Vault-Token:...

Thanks for providing that information. One additional question, are you using any proxying when accessing Vault, including perhaps vault proxy or vault agent in proxy mode?

Unfortunately I still can't reproduce this. I was thinking that perhaps the `Origin` header wasn't getting forwarded to Vault, but I agree that it seems unlikely if you're experiencing no...

> This is what I get from curl: > ```sh > < HTTP/2 404 > HTTP/2 404 > < alt-svc: h3=":443"; ma=2592000 > alt-svc: h3=":443"; ma=2592000 > < cache-control: no-store...