Idea ID 2786104


The AAF 6.2 product contains an SMS TOTP method preconfigured for MessageBird. Which is great.

However, the method uses the "OLD HTTP-API_v1" as MessageBird refers to it and is dated somewhere in 2014.
This method forces one to use a usename/password setup.
The new and current MessageBird API (v2) uses an API key for authenticating.

To keep the adoption level low, i'd recommend to add an additional method to AAF for MessageBird which uses an API key.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.