AWS IoT MQTT Custom Authentication

​From sgcWebSockets 4.4.3, Amazon AWS IoT MQTT component supports custom authentication, so from this version all MQTT protocols are supported.

1. MQTT over WebSockets
2. MQTT over TCP
3. X.509 certificate authentication
4. Signature V4 authentication
5. Custom Authentication

 The following table lists the protocols that the AWS IoT device endpoints support and the authentication methods and ports they use.

AWS IoT Core lets you define custom authorizers so that you can manage your own client authentication and authorization. This is useful when you need to use authentication mechanisms other than the ones that AWS IoT Core natively supports. For example, if you are migrating existing devices in the field to AWS IoT Core and these devices use a custom bearer token or MQTT user name and password to authenticate, you can migrate them to AWS IoT Core without having to provision new identities for them. You can use custom authentication with any of the communication protocols that AWS IoT Core supports.

Example: if you want to use MQTT username and password to authenticate

Example: if you want to send a bearer token

Delphi Amazon AWS IoT Client Component