Cara mengonfigurasi TLS untuk Cassandra di platform runtime
Cassandra menyediakan komunikasi yang aman antara mesin klien dan cluster database serta antara node dalam cluster. Mengaktifkan enkripsi memastikan bahwa data
dalam pengiriman tidak disusupi dan ditransfer dengan aman. Di Apigee hybrid, TLS diaktifkan secara default untuk semua komunikasi antara node Cassandra dan antara klien dan node Cassandra.
Tentang autentikasi pengguna Cassandra
Platform campuran menggunakan Cassandra sebagai datastore backend untuk data
bidang runtime. Secara default, setiap komunikasi klien ke Cassandra
memerlukan autentikasi. Ada tiga pengguna yang digunakan oleh klien yang berkomunikasi
dengan Cassandra. Sandi default disediakan untuk pengguna ini, dan Anda tidak
diwajibkan untuk mengubahnya.
Pengguna ini,
termasuk pengguna default, dijelaskan di bawah ini:
Pengguna DML: Digunakan oleh komunikasi klien untuk membaca dan menulis data ke Cassandra
(KMS, KVM, Cache, dan Kuota).
Pengguna DDL: Digunakan oleh MART untuk tugas definisi data apa pun seperti pembuatan, pembaruan, dan penghapusan keyspace.
Pengguna Admin: Digunakan untuk aktivitas administratif apa pun yang dilakukan
di cluster cassandra.
Pengguna Cassandra default: Cassandra membuat pengguna default saat
Autentikasi diaktifkan dan nama penggunanya adalah cassandra
Mengubah sandi default
Apigee hybrid menyediakan sandi default untuk pengguna Cassandra. Jika ingin mengubah
sandi pengguna default, Anda dapat melakukannya di
file overrides.yaml. Tambahkan konfigurasi berikut, ubah sandi default ("iloveapis123") sesuai keinginan, dan terapkan perubahan ke cluster Anda.
Sertifikat server yang dibuat dengan frasa sandi tidak didukung.
Memeriksa log Cassandra
Periksa log segera setelah Cassandra dimulai. Log di bawah menunjukkan bahwa koneksi klien Cassandra dienkripsi.
kubectl logs apigee-cassandra-2 -n apigee -f
INFO 00:44:36 Starting listening for CQL clients on /10.0.2.12:9042 (encrypted)...
INFO 00:44:36 Binding thrift service to /10.0.2.12:9160
INFO 00:44:36 enabling encrypted thrift connections between client and server
INFO 00:44:36 Listening for thrift clients...
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis documentation version (1.2) for Apigee hybrid is end-of-life, and users should upgrade to a newer, supported version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid uses Cassandra as the backend datastore, and TLS encryption is enabled by default for communication between Cassandra nodes and clients.\u003c/p\u003e\n"],["\u003cp\u003eThere are three default user accounts (DML, DDL, and Admin) for client communication with Cassandra, along with a default "cassandra" user account, and while default passwords are provided, users can change them in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eCassandra client connections are encrypted, as confirmed by checking the Cassandra logs after startup.\u003c/p\u003e\n"],["\u003cp\u003eCertificate Authority rotation and server certificates with a passphrase are not supported.\u003c/p\u003e\n"]]],[],null,["# Configuring TLS for Cassandra\n\n| You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nHow to configure TLS for Cassandra in the runtime plane\n-------------------------------------------------------\n\n\nCassandra provides secure communication between a client machine and a database\ncluster and between nodes within a cluster. Enabling encryption ensures that data\nin flight is not compromised and is transferred securely. In Apigee hybrid, TLS is\nenabled by default for any communication between Cassandra nodes and between clients and\nCassandra nodes.\n\nAbout Cassandra user authentication\n-----------------------------------\n\n\nThe hybrid platform uses Cassandra as the backend datastore for runtime\nplane data. By default, any of the client communications to Cassandra\nrequires authentication. There are three users used by clients that communicate\nwith Cassandra. Default passwords are provided for these users, and you are not\nrequired to change them.\n\nThese users,\nincluding a default user, are described below:\n\n- **DML User**: Used by the client communication to read and write data to Cassandra (KMS, KVM, Cahce and Quota).\n- **DDL User:** Used by MART for any of the data definition tasks like keyspace creation, update, and deletion.\n- **Admin User:** Used for any administrative activities performed on cassandra cluster.\n- **Default Cassandra user:** Cassandra creates a default user when Authentication is enabled and the username is `cassandra`\n\nChanging the default passwords\n------------------------------\n\n\nApigee hybrid provides default passwords for the Cassandra users. If you want to change\nthe default user passwords, you can do so in the\n`overrides.yaml` file. Add the following configuration, change the default\npasswords (\"iloveapis123\") as you wish, and apply the change to\nyour cluster.\n\n\nAll the usernames must be in lowercase. \n\n```actionscript-3\ncassandra:\n auth:\n default: ## the password for the new default user (static username: cassandra)\n password: \"iloveapis123\"\n admin: ## the password for the admin user (static username: admin_user)\n password: \"iloveapis123\"\n ddl: ## the password for the DDL User (static username: ddl_user)\n password: \"iloveapis123\"\n dml: ## the password for the DML User (static username: dml_user)\n password: \"iloveapis123\"\n```\n\n\nNote the following:\n\n- Certificate Authority (CA) rotation is not supported.\n- A server certificate which is generated with passphrase is not supported.\n\nCheck the Cassandra logs\n------------------------\n\n\nCheck the logs as soon as the Cassandra starts up. The log below shows you that the\nCassandra client connections are encrypted. \n\n```\nkubectl logs apigee-cassandra-2 -n apigee -f\n\nINFO 00:44:36 Starting listening for CQL clients on /10.0.2.12:9042 (encrypted)...\nINFO 00:44:36 Binding thrift service to /10.0.2.12:9160\nINFO 00:44:36 enabling encrypted thrift connections between client and server\nINFO 00:44:36 Listening for thrift clients...\n```"]]
