CompanyOnwership_icon
LINKIT R&D
Created on 15 March 2022
icon_unfollowing
Login to follow
vonage-2fa

Vonage 2FA

Stable version 2.0.1 (Compatible with OutSystems 11)
Uploaded on 07 October 2022 by 
LINKIT R&D
vonage-2fa

Vonage 2FA

Documentation
2.0.1

VONAGE 2FA

Documentation:

Vonage:

- Getting started

Vonage2FA_API:

- Authorization

- Version 1

- Version 2 (beta)

Vonage2FA:

- 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.


VONAGE2FA_API – AUTHORIZATION

Inside the Vonage2FA_API module, we have created two site properties; one for the API Key and one for the API Secret.

Both are needed for proper authorization.

VONAGE2FA_API – VERSION 1

We created wrapper server actions for calling the REST API

VONAGE2FA_API – VERSION 2

We created wrapper server actions for calling the REST API


VONAGE 2FA – VERSION 1

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

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

VONAGE 2FA – VERSION 1

The Check_WB is used to check the retrieved code.

The Vonage2FA screen inside the demo shows a simple example of how these two webblocks could work together.

VONAGE 2FA – VERSION 2

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

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


VONAGE 2FA – VERSION 2

The Check_WB is used to check the retrieved code.

The Verify2 screen inside the demo application shows a simple example of how these two webblocks could work together.


2.0.0

VONAGE VIDEO

Documentation:

Vonage:

- Getting started

Vonage2FA_API:

- Authorization

- Version 1

- Version 2 (beta)

Vonage2FA:

- 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.


VONAGE2FA_API – AUTHORIZATION

Inside the Vonage2FA_API module, we have created two site properties; one for the API Key and one for the API Secret.

Both are needed for proper authorization.

VONAGE2FA_API – VERSION 1

We created wrapper server actions for calling the REST API

VONAGE2FA_API – VERSION 2

We created wrapper server actions for calling the REST API


VONAGE 2FA – VERSION 1

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

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

VONAGE 2FA – VERSION 1

The Check_WB is used to check the retrieved code.

The Vonage2FA screen shows a simple example of how these two webblocks could work together.

VONAGE 2FA – VERSION 2

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

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

VONAGE 2FA – VERSION 2

The Check_WB is used to check the retrieved code.

The Verify2 screen shows a simple example of how these two webblocks could work together.


Support options
This asset is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from  who created this asset.
Dependencies
See all 1 dependencies