Starlight for RabbitMQ security
Starlight for RabbitMQ supports connections using TLS/mTLS to ensure privacy and security of the communication.
It also supports the PLAIN and EXTERNAL authentication mechanisms used by RabbitMQ:
-
PLAIN: Maps to theAuthenticationProviderTokenmode of authentication. Theusernameis ignored, and thepasswordis used as the JSON Web Token (JWT). -
EXTERNAL: Maps to theAuthenticationProviderTlsmode of authentication. This is the equivalent of therabbitmq-auth-mechanism-sslplugin withssl_cert_login_fromparameter set tocommon_name.
Internally, it uses the same AuthenticationService as Pulsar, and it maps these mechanisms to existing Pulsar authentication modes.
Starlight for RabbitMQ doesn’t support authorization.
This means an authenticated user has full access to all Virtual hosts.
Starlight for RabbitMQ can connect to brokers that have TLS, authentication, and/or authorization enabled.
To perform its operations, Starlight for RabbitMQ proxy must use an admin role.
