Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from 1.12.0 to 1.13.0 causes Error 403 (Forbidden) #1641

Closed
wsoula opened this issue Jun 27, 2019 · 3 comments · Fixed by #1642
Closed

Upgrade from 1.12.0 to 1.13.0 causes Error 403 (Forbidden) #1641

wsoula opened this issue Jun 27, 2019 · 3 comments · Fixed by #1642

Comments

@wsoula
Copy link

wsoula commented Jun 27, 2019

Requirement - what kind of business use case are you trying to solve?

Track traces

Problem - what in Jaeger blocks you from solving the requirement?

image
If I rollback to 1.12.0 then it works again

Proposal - what do you suggest to solve the problem or improve the existing situation?

Any open questions to address

@wsoula
Copy link
Author

wsoula commented Jun 27, 2019

Appears env var QUERY_BEARER_TOKEN_PROPAGATION=false allows it to work.

@wsoula wsoula closed this as completed Jun 27, 2019
@yurishkuro
Copy link
Member

This is a bug, false value should be the default

@yurishkuro yurishkuro reopened this Jun 27, 2019
wsoula pushed a commit to wsoula/jaeger that referenced this issue Jun 28, 2019
To false for backwards compatibility
Fixes jaegertracing#1641
wsoula pushed a commit to wsoula/jaeger that referenced this issue Jun 28, 2019
To false for backwards compatibility
Fixes jaegertracing#1641

Signed-off-by: Will Soula <[email protected]>
@pavolloffay
Copy link
Member

thanks for reporting @wsoula.

I will push 1.13.1 with your fix

pavolloffay pushed a commit that referenced this issue Jun 28, 2019
To false for backwards compatibility
Fixes #1641

Signed-off-by: Will Soula <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants