Does this seem right (attached screenshot)? In the browser’s network tab, I can see the HTTP 201 request and the response JSON does actually contain a token. However, if I use it via Authorization: Bearer <tkn> header, it doesn’t work. What’s going on?
Quite sure you are using version 20.10.0 which has a build bug. We have released 20.10.1 right after and upgrading to that should resolve this.
Thanks - that was the problem. Pretty strange bug, though.
1 Like
Yeah, our acceptance tests used the CI environment variable to “fix” dynamic strings so we have consistent screenshot tests. We changed a few things around our OSS build pipelines which also set this variable but for different reasons and the result is a build that thinks it is in testing mode 
1 Like