-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error/warn if TLS flags are used when tls.enabled=false #2893
Comments
+1 to crash |
I would like to pick this one up. Is there a consensus that this incorrect configuration should be fatal? |
@LostLaser I think an incorrect configuration should be fatal rather than just being logged and my understanding is @yurishkuro is on the same page (but please correct me if I'm wrong). |
Agreed |
@LostLaser it's yours :-) |
is there activity on this issue? if not can I take this over? |
@LostLaser are you okay with @clock21am taking over this task? |
Yes, that’s fine! Sorry for the delay. |
it should fail for both clients and sever side if I am not right? |
IIUC, the TLS flags should only apply to the server side, and so should fail for just the server side. |
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
This commit adds tls flag test in collector/app/builder_flag_test.go and query/app/flag_test.go Also fixes InitFromViper check in builder_flag.go (jaegertracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
This commit adds tls flag test in collector/app/builder_flag_test.go and query/app/flag_test.go Also fixes InitFromViper check in builder_flag.go (jaegertracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
This commit adds tls flag test in collector/app/builder_flag_test.go and query/app/flag_test.go Also fixes InitFromViper check in builder_flag.go (jaegertracing#2893) Signed-off-by: Rajdeep Kaur <rajdeep51994@gmail.com>
…tracing#2893 (jaegertracing#3030) Signed-off-by: Albert Teoh <see.kwang.teoh@gmail.com>
Requirement - what kind of business use case are you trying to solve?
Motivated by this comment in Slack:
Problem - what in Jaeger blocks you from solving the requirement?
The user was, rightfully, confused when the
--es.tls.skip-host-verify
was set but wasn't working.Proposal - what do you suggest to solve the problem or improve the existing situation?
Log a warning or error if any
--*.tls.*
flag is set when--*.tls.enabled == false
, maybe somewhere here and here.Any open questions to address
Should we log a warning or error (and prevent startup of service)? I would lean towards the latter to be more explicit, though I think it would be considered "breaking" behaviour. The former warning could be easily missed.
The text was updated successfully, but these errors were encountered: