Language and Framework | Demo Address | Reference Documentation |
Java | ||
Python | ||
Go | ||
PHP | ||
C++ | ||
Node.js |
Protocol Type | Protocol Description | Supported by the VPC Network or Not | Supported by the Public Network or Not |
PLAINTEXT | Authentication is not required for message sending and receiving, and data is transmitted in plaintext. | ✓ | × |
SASL_PLAINTEXT | SASL authentication is required for message sending and receiving, and data is transmitted in plaintext, showing higher performance. | ✓ | ✓ |
SASL_SSL | SASL authentication is required for message sending and receiving, and data is encrypted using SSL certificates for transmission to prevent interception or eavesdropping, showing higher security. | ✓ (Only supported by Pro Edition, and not supported by version 3.2.3 currently) | ✓ (Only supported by Pro Edition, and not supported by version 3.2.3 currently) |
SASL_SCRAM_SHA_256 | SASL authentication is required for message sending and receiving. Passwords are stored using a hash algorithm (SHA-256) and not transmitted in plaintext. Data is transmitted in plaintext. | ✓ (Only supported by instances of versions 1.1.1, 2.4.1, and 2.8.1. For existing instances, you need to upgrade the broker minor version or submit a ticket to apply for the upgrade.) | × |
SASL_SCRAM_SHA_512 | SASL authentication is required for message sending and receiving. Passwords are stored using a hash algorithm (SHA-512) and not transmitted in plaintext. Data is transmitted in plaintext. Compared to SHA-256, SHA-512 provides higher security but consumes more computing resources. | ✓ (Only supported by instances of versions 1.1.1, 2.4.1, and 2.8.1. For existing instances, you need to upgrade the broker minor version or submit a ticket to apply for the upgrade.) | × |

instance ID + # + configured username. The password is the one set when the user is created.

Feedback