After setting up the API with appropriate environment variables to be able to log in, the Admin first prompts me to log in. I enter matching credentials, it works and I'm on the token management screen. However, when I attempt to create a new token, I get an error message where the root cause is that the API returned a 401.
I suspect the issue is that the Admin is assuming that Authorization headers will automatically be propagated when accessing the API, but that relies on the assumption that they're hosted on the same server.
After setting up the API with appropriate environment variables to be able to log in, the Admin first prompts me to log in. I enter matching credentials, it works and I'm on the token management screen. However, when I attempt to create a new token, I get an error message where the root cause is that the API returned a 401.
I suspect the issue is that the Admin is assuming that
Authorizationheaders will automatically be propagated when accessing the API, but that relies on the assumption that they're hosted on the same server.