Cloud Account Creation - Differences Between Email and Social-based Authentication

Account Creation

When creating a HiveMQ Cloud account, there are a few additional details to note based on the authentication method that is used for the creation of the account.

E-mail-based Authentication

When utilizing an e-mail based authentication method, HiveMQ is responsible for performing authentication, and as a result will have a record of email, and credentials utilized for the creation of the account.

This means that :

• Password reset requests can be performed directly via HiveMQ.

• Invitations to other existing clusters, such as another organization, can be sent directly via email.

• Initial verification will be sent via e-mail to the associated email address.

Social-based Authentication

When utilizing a social platform, such as Google, GitHub, or LinkedIn to authenticate for HiveMQ Cloud, these platforms are utilized to provide authentication for the account. This results in a few additional scenarios that are worth noting.

• If using a Google account, Google is responsible for authentication, and the email associated with this account is not utilized by HiveMQ.

  • This means that if you attempt to log in with the same email that is associated with the Google authentication, you will be prompted to create an email based account.

  • When using Google-based authentication, ensure that you are consistently choosing to authenticate with Google, rather than swapping between Google-based authentication, and Email-based authentication.

• If using a Social-based authentication, and an email-based account has been created for an account with a matching email, this email-based account will take precedence when receiving an organization invite.