Skip to content

Commit 23be225

Browse files
Fix technical detail - gRPC with TLS != HTTPS necessarily.
Signed-off-by: Finn Carroll <carrofin@amazon.com>
1 parent 6000fac commit 23be225

File tree

1 file changed

+1
-1
lines changed
  • _security/authentication-backends

1 file changed

+1
-1
lines changed

_security/authentication-backends/jwt.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -341,7 +341,7 @@ Starting with OpenSearch 3.5, JWT authentication is supported over the gRPC tran
341341
- Superuser authentication (client certificate authentication) is not supported over gRPC. Configuration changes requiring superuser privileges should use the REST API.
342342
- Anonymous authentication is not supported over gRPC. Requests with anonymous authentication headers are rejected as unauthorized.
343343

344-
You should use HTTPS instead of HTTP when transmitting JWTs over gRPC. For information about configuring TLS for gRPC, see [Configuring TLS certificates for gRPC]({{site.url}}{{site.baseurl}}/security/configuration/tls/#configuring-tls-certificates-for-grpc).
344+
You should enable TLS when transmitting JWTs over gRPC. For information about configuring TLS for gRPC, see [Configuring TLS certificates for gRPC]({{site.url}}{{site.baseurl}}/security/configuration/tls/#configuring-tls-certificates-for-grpc).
345345

346346

347347
## Troubleshooting common issues

0 commit comments

Comments
 (0)