The response body is {"errors":[]} whereas it would normally return more info like unsupported path or operation not permitted, so it seems to be recognizing the path but something else is going on. However I can’t find any mention of trouble with this endpoint online or in these forums so hoping someone can help.
Thanks for the response, which shows an empty response is to be expected if no custom headers have been set.
However, there clearly are default headers, which various docs and tutorials reference this endpoint to discover if not in the Vault configuration file. If those references are incorrect, where can I find what the default headers are?
Sure, that’s what I was doing which led me down this path. It’s just confusing and a little frustrating as a new Vault user when the documentation and tutorials are wrong.
Regardless, thanks for clearing it up for me @aram.