Skip to content

DOC-1855 SR support for SASL/PLAIN in SM #1510

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.

Sign up for GitHub

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

Merged
micheleRP merged 2 commits into from
Dec 10, 2025
Merged

DOC-1855 SR support for SASL/PLAIN in SM #1510

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f0c4b8
DOC-1855 SR support for SASL/PLAIN in SM
micheleRP Dec 9, 2025
43f9518
revert playbook
micheleRP Dec 10, 2025
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
16 changes: 15 additions & 1 deletion modules/manage/pages/disaster-recovery/shadowing/setup.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ This service account authenticates from the shadow cluster to the source cluster
You must configure network connectivity between clusters with appropriate firewall rules to allow the shadow cluster to connect to the source cluster for data replication. Shadowing uses a pull-based architecture where the shadow cluster fetches data from the source cluster. For detailed networking configuration, see <<networking>>.

ifndef::env-cloud[]
If using xref:manage:security/authentication.adoc[authentication] for the shadow link connection, configure the source cluster with your chosen authentication method (SASL/SCRAM, TLS, mTLS) and ensure the shadow cluster has the proper credentials to authenticate to the source cluster.
If using xref:manage:security/authentication.adoc[authentication] for the shadow link connection, configure the source cluster with your chosen authentication method (SASL/SCRAM, SASL/PLAIN, TLS, mTLS) and ensure the shadow cluster has the proper credentials to authenticate to the source cluster.
endif::[]

ifdef::env-cloud[]
Expand Down Expand Up @@ -156,10 +156,17 @@ client_options:
do_not_set_sni_hostname: false # Optional: Skip SNI hostname when using TLS (default: false)

authentication_configuration:
# SASL/SCRAM authentication
scram_configuration:
username: <sasl-username> # SASL/SCRAM username, example: "shadow-replication-user"
password: <sasl-password> # SASL/SCRAM password, example: "secure-password-123"
scram_mechanism: SCRAM_SHA_256 # SCRAM mechanism: "SCRAM_SHA_256" or "SCRAM_SHA_512"
ifndef::env-cloud[]
# SASL/PLAIN authentication
plain_configuration:
username: <sasl-username> # SASL/PLAIN username, example: "shadow-replication-user"
password: <sasl-password> # SASL/PLAIN password, example: "secure-password-123"
endif::[]

# Connection tuning - adjust based on network characteristics
metadata_max_age_ms: 10000 # How often to refresh cluster metadata (default: 10000ms)
Expand Down Expand Up @@ -476,10 +483,17 @@ client_options:
----
client_options:
authentication_configuration:
# SASL/SCRAM authentication
scram_configuration:
username: <sasl-username> # SASL/SCRAM username, example: "shadow-replication-user"
password: <sasl-password> # SASL/SCRAM password, example: "secure-password-123"
scram_mechanism: SCRAM_SHA_256 # SCRAM mechanism: "SCRAM_SHA_256" or "SCRAM_SHA_512"
ifndef::env-cloud[]
# SASL/PLAIN authentication
plain_configuration:
username: <sasl-username> # SASL/PLAIN username, example: "shadow-replication-user"
password: <sasl-password> # SASL/PLAIN password, example: "secure-password-123"
endif::[]
----

==== Connection tuning
Expand Down