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

Clarified consumer-to-query security support. #522

Merged
merged 2 commits into from
Aug 25, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/1.22/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Clients can be configured to communicate directly with the Collector via HTTP. U

## Consumers to Query Service

* {{< check_yes >}} HTTP - no TLS/authentication.
* {{< check_yes >}} gRPC - no TLS/authentication.
* {{< check_yes >}} HTTP - TLS with client cert authentication supported.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we could use the same text as for Cassandra above: "TLS with mTLS supported"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was using the same text from the Agent to Collector section for gRPC. Should I switch them all to "TLS with mTLS supported" ?

* {{< check_yes >}} gRPC - TLS with client cert authentication supported.

[issue-1718]: https://github.com/jaegertracing/jaeger/issues/1718
4 changes: 2 additions & 2 deletions content/docs/1.23/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Clients can be configured to communicate directly with the Collector via HTTP. U

## Consumers to Query Service

* {{< check_yes >}} HTTP - no TLS/authentication.
* {{< check_yes >}} gRPC - no TLS/authentication.
* {{< check_yes >}} HTTP - TLS with client cert authentication supported.
* {{< check_yes >}} gRPC - TLS with client cert authentication supported.

[issue-1718]: https://github.com/jaegertracing/jaeger/issues/1718
4 changes: 2 additions & 2 deletions content/docs/1.24/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Clients can be configured to communicate directly with the Collector via HTTP. U

## Consumers to Query Service

* {{< check_yes >}} HTTP - no TLS/authentication.
* {{< check_yes >}} gRPC - no TLS/authentication.
* {{< check_yes >}} HTTP - TLS with client cert authentication supported.
* {{< check_yes >}} gRPC - TLS with client cert authentication supported.

[issue-1718]: https://github.com/jaegertracing/jaeger/issues/1718
4 changes: 2 additions & 2 deletions content/docs/1.25/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Clients can be configured to communicate directly with the Collector via HTTP. U

## Consumers to Query Service

* {{< check_yes >}} HTTP - no TLS/authentication.
* {{< check_yes >}} gRPC - no TLS/authentication.
* {{< check_yes >}} HTTP - TLS with client cert authentication supported.
* {{< check_yes >}} gRPC - TLS with client cert authentication supported.

[issue-1718]: https://github.com/jaegertracing/jaeger/issues/1718
4 changes: 2 additions & 2 deletions content/docs/next-release/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Clients can be configured to communicate directly with the Collector via HTTP. U

## Consumers to Query Service

* {{< check_yes >}} HTTP - no TLS/authentication.
* {{< check_yes >}} gRPC - no TLS/authentication.
* {{< check_yes >}} HTTP - TLS with client cert authentication supported.
* {{< check_yes >}} gRPC - TLS with client cert authentication supported.

[issue-1718]: https://github.com/jaegertracing/jaeger/issues/1718