Details
Description
today we allow both unencrypted and encrypted communication (SSL / TLS) and one can use firewalls to control which one stays available to communicating with couchbase server. it would be great to have a way to enforce secure communication through a switch and disable any unencrypted access to help compliance with security standards easily.
Attachments
Issue Links
- depends on
-
MB-48030 [BP to 7.0.2] [TLS] Strict mode, see errors in query log for 9101 port for indexer client
- Closed
-
MB-42364 Enforce TLS - FTS
- Closed
-
MB-42372 Enforce TLS - memcached
- Closed
-
MB-42373 Enforce TLS - NS-Server
- Closed
-
MB-43151 Enforce TLS -UI
- Closed
-
MB-42365 Enforce TLS - Eventing
- Closed
-
MB-42366 Enforce TLS - Views
- Closed
-
MB-42368 Enforce TLS - Query
- Closed
-
MB-42369 Enforce TLS - Analytics
- Closed
-
MB-42370 Enforce TLS - Indexing
- Closed
-
MB-42371 Enforce TLS - XDCR
- Closed
-
MB-43102 Crypto: Enforce TLS API
- Closed
-
MB-43150 Enforce TLS - couchbase-cli
- Closed
-
MB-46176 Enforce TLS - Backup & Backup Service
- Closed
-
MB-47096 REST API support for HSTS response headers
- Closed
-
MB-47101 CLI support for HSTS response headers
- Closed
- is duplicated by
-
MB-14843 Disable the unencrypted HTTP port 8091
- Closed
-
MB-22907 Disabling REST Access over HTTP
- Closed
-
MB-23960 Ability to Completely Disable all Communication over port 8091
- Closed
- relates to
-
MB-14842 Disable the unencrypted memcached TCP port 11211
- Closed
-
K8S-2178 CAO - Enforce TLS Only
- Closed
-
MB-39345 Control who can use unencrypted communication
- Closed
- mentioned in
-
Page Loading...