How is your experience with the OutSystems Community?
Vonage 2FA

Vonage 2FA (ODC)

Stable version 1.1.0 (Compatible with ODC)
Uploaded on 30 April 2024 by LINKIT
Vonage 2FA

Vonage 2FA (ODC)

Documentation
1.1.0

Documentation:


Vonage:

  • Getting started;
  • https://www.vonage.com/communications-apis/

Vonage 2FA APIs:

  • Authorization
  • Version 1
  • Version 2 (beta)

Vonage 2FA reusable blocks:

  • Version 1
  • Version 2 (beta)


VONAGE – GETTING STARTED


To use the LINKIT Vonage components, you’ll need to create a so called ‘Nexmo’ account: https://developer.vonage.com/account/guides/dashboard-management#create-andconfigure-a-nexmo-account

Creating an account will give you some credits as well as a personal API Key and API Secret.

You need these to get your application up and running.


VONAGE 2FA APIs – AUTHORIZATION

Inside the Vonage 2FA library, we have created two settings; one for the API Key and one for the API Secret.

Both are needed for proper authorization.


VONAGE 2FA APIs – VERSION 1

We created wrapper server actions for calling the REST API




VONAGE 2FA APIs – VERSION 2

We created wrapper server actions for calling the REST API


VONAGE 2FA REUSABLE BLOCKS – VERSION 1

To use Vonage 2FA, there’s two blocks to be used: Vonage2FA_Request_WB and Vonage2FA_Check_WB.

The Check_WB is used to check the retrieved code.

On the Request_WB, the necessary variables for a request are being mapped, with Number, Workflow and Brand being mandatory.


VONAGE 2FA REUSABLE BLOCKS – VERSION 2

To use Vonage 2FA v2, there’s two blocks to be used: Verify2_Request_WB and Verify2_Check_WB.

The Check_WB is used to check the retrieved code.

On the Request_WB, the necessary variables for a request are being mapped, with Number, Channel and Brand being mandatory.


NOTE: when this component was first created, 'Verify v2' was a new version of the existing Verify API that's already implemented in our component, with new features and capabilities, mostly notably using the WhatsApp channel for sending one-time passcodes. We decided not to replace the Verify API (v1), but just to add the v2 to the component. Consumers can choose which version they want to use.