Assistance Needed with Certificate Authentication using MQTT in Solace AEM for iOS mobile app

Connectors & Integrations
1

Hi Team,

Could you please provide guidance on how to implement certificate-based authentication for MQTT clients within the Solace Advanced Event Mesh (AEM) framework to iOS mobile app implement? Specifically, I’m looking for the recommended steps or best practices to configure and enable certificate authentication for MQTT connections.

Thank you for your support!

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Let me analyze how to implement certificate-based authentication for MQTT clients within Solace software broker for an iOS mobile app.

The implementation requires several key steps:

  1. Certificate Setup:
  • Create an internal Certificate Authority (CA) using OpenSSL
  • Generate a client certificate signed by the CA
  • Keep the client private key secure
  1. Event Broker Configuration:
  • Enable client certificate authentication in the Message VPN
  • Upload the CA certificate to the broker’s trusted CA list
  • Configure username source (Common Name or Subject Alternative Name)
  • Configure the MQTT service to use TLS port (typically 8883)
  1. iOS Client Implementation:
  • Use TLS/SSL for secure MQTT connections
  • Configure the client certificate and private key
  • Connect using port 8883 for secure MQTT

Here are the relevant sources for detailed implementation steps:

Important considerations:

  • The broker must be configured to use TLS by setting a server certificate
  • Client certificates must be in PEM format
  • The MQTT service must be enabled and configured for TLS connections
  • The client username must match the certificate’s Common Name or Subject Alternative Name based on configuration
  • For iOS apps, ensure proper certificate handling and secure storage of private keys

For specific iOS implementation details and sample code, refer to the Solace documentation for mobile development.