Talk To Us!
Authentication
Aculab Cloud uses these types of credentials:
| Credential | Purpose | User-defined |
|---|---|---|
| Cloud Console | Used to login to the Cloud Console | Yes |
| Outbound service | Assigned to each individual outbound service | Yes |
| API Access Key | Generated key to access the REST, UAS and Web Service APIs | No |
| WebRTC Access Key | Generated key to access the WebRTC API | No |
| Voice Biometric User Group Key | Generated key to access the Voice Biometric User API | No |
Cloud Console login
The Cloud Console login requires a password to access the Cloud Console website, in order to provide account information, usage reports, add funds, buy telephone numbers, create and modify services and much more. Due to the nature of the data available on the site it's important to keep your website password confidental and unique. To improve the complexity of the password, we enforce these type of passwords to be at least seven characters in length, with at least one letter or number.
Multi-factor authentication
You can add extra security to your Cloud Console login by setting up Multi-Factor Authentication (MFA). This requires a second authorisation method in addition to your password. You can enable MFA in the Security credentials page.
When MFA is enabled, signing into the Cloud Console prompts you for your username and password, and also an authentication code from an authenticator app on your MFA device.
You can download and use any authenticator app that implements the time-based one-time password (TOTP) algorithm. Here are some examples of compatible authenticator apps:
- Google Authenticator (Android, iOS)
- Microsoft Authenticator (Android, iOS)
- LastPass Authenticator (Android, iOS)
- Symantec VIP
Outbound Service password
A password is assigned to each outbound service you create. When invoking an outbound service, the outbound service password is authenticated before starting the application. There are no restictions on the password. It is advised to have unique passwords for each outbound service, and for the password to be different to your Cloud Console password.
API Access Key
The UAS and web services, other than starting an outbound service, will use the API Access Key for authentication. The Key itself can be viewed from the Security credentials page, accessible via the Cloud Console. Here you can view the Key and optionally generate a new one. It is not possible to set your own Key.
Accounts created before the introduction of the API Access Key will have their Key automatically defaulted to be the Cloud Console password. This ensure backwards compatibility with your existing setup. However, it is recommended to generate a new Key to use in your code.
You may replace your key by generating a new one using the Cloud Console. The newly generated key can be displayed on screen, but the previous one will continue to operate. Once you have made the necessary changes in your code, the newly generated Key can be used immediately after. The previously used key will then no longer work.
WebRTC Access Key
When creating a client via the WebRTC API you will need to provide the WebRTC Access Key associated with your account. The key is available to copy from the Security credentials page of the Cloud Console. It is not possible to set your own key.
Voice Biometrics User Group Key
The Voice Biometrics User API web services require a key associated with a particular Voice Biometrics user group for authentication. You can generate new user group keys via the Cloud Console. You can temporarily disable your user group keys or delete them.
