Authentication
Overview
To connect to Newline’s Message Queue (MQ), clients must authenticate using credentials provided during onboarding. All connections must be secured via SSL/TLS, and clients must choose a supported protocol that fits their infrastructure.
Credentials
After defining your subscription topics, Newline will issue:
- Username and Password: Used to authenticate your MQ connection.
- Topic Prefixes: Required for topic subscription formatting.
- Host and Port Details: Based on your selected protocol.
Secure Connection Requirements
All MQ connections must:
- Use SSL/TLS encryption
- Connect to the appropriate sandbox or production endpoint
- Include protocol-specific headers (e.g.,
client-id
,subscriptionName
for STOMP)
Sandbox Endpoints
Use these endpoints for testing in the sandbox environment:
Protocol | Endpoint |
---|---|
OpenWire | ssl://mq-sandbox.newline53.com:61617 |
AMQP | amqp+ssl://mq-sandbox.newline53.com:5671 |
STOMP | stomp+ssl://mq-sandbox.newline53.com:61614 |
MQTT | mqtt+ssl://mq-sandbox.newline53.com:8883 |
WSS | wss://mq-sandbox.newline53.com:61619 |
Production Endpoints
Use these endpoints for live production traffic:
Protocol | Endpoint |
---|---|
OpenWire | ssl://mq.newline53.com:61617 |
AMQP | amqp+ssl://mq.newline53.com:5671 |
STOMP | stomp+ssl://mq.newline53.com:61614 |
MQTT | mqtt+ssl://mq.newline53.com:8883 |
WSS | wss://mq.newline53.com:61619 |
Tips for Implementation
- Ensure your client supports the selected protocol and SSL/TLS.
- Use durable subscriptions for fault tolerance.
- Include client-id and subscriptionName headers when using STOMP.
Updated 1 day ago