Authenticate a login with Temenos
If your user has already registered a second-factor authenticator, they can use it to authenticate a login operation. On this page, you can find the following login authentication use cases: authentication using only a mobile banking app, and passwordless login using a mobile banking app and your web banking application.
Authentication using a mobile banking app
In this use case, a mobile banking app is used to authenticate a login. The following step list shows the high-level workflow:
- The user opens the mobile banking app and attempts to log in.
- The user is prompted to authenticate themselves with a PIN or biometric data.
- The mobile banking app authenticates the user with the help of Nevis Mobile Authentication SDK and Authentication Cloud.
- The mobile banking app receives the authentication confirmation.
The following diagram shows a more detailed example of an end-to-end sequence of authenticating a login using a mobile banking app. In this example, both the Nevis status token and the Infinity Fabric token are sent and verified in the resource request. However, the resource request can be made only with a Fabric Token.
The diagram includes customer, Temenos, and Authentication Cloud functions, with the following color coding:
- Gray: Customer functions
- Yellow: Temenos functions
- Blue: Nevis Mobile Authentication SDK and Authentication Cloud functions
The SDK is integrated into the mobile banking app.
Authentication Cloud functions include API calls to authenticate the operation and to verify the status token. For more information about these calls, see Authenticate transactions with QR code or deep link and Authenticate transactions with push notification.
Passwordless login using a mobile banking app and a web banking application
In this use case, the user logs in only with their username, and both a mobile banking app and the web banking application are used to authenticate the login. Either a QR code or a push message, or both can be used for authentication. The following step list shows the high-level workflow:
- The user opens the web banking application.
- The web banking application requests the username.
- The web banking application performs one or both of the following actions:
- Presents a QR code that the user must read with the mobile banking app.
- Sends a push message to the mobile banking app and presents the codes for number matching.
- The user authenticates the login with PIN or biometric data using the mobile banking app.
- The web banking application logs the user in.
The Authentication with QR code and Authentication with push message diagrams show more detailed examples of passwordless login authentication end-to-end sequences. The diagrams include customer, Temenos, and Authentication Cloud functions, with the following color coding:
- Gray: Customer functions
- Yellow: Temenos functions
- Blue: Nevis Mobile Authentication SDK and Authentication Cloud functions
The SDK is integrated into the mobile banking app.
Authentication with QR code
In this use case, the user is presented with a QR code, and by reading QR code, they initiate the authentication.
Authentication Cloud functions include API calls to initiate the authentication, verify the status token, and optionally, to get the username. For more information about these calls, see Authenticate transactions with QR code and Retrieve a user.
Authentication with push message
In this use case, the user receives a push message that initiates the authentication. For added security, you can use the optional number matching feature.
Authentication Cloud functions include API calls to initiate the authentication, verify the status token, and optionally, to get the username. For more information about these calls, see Authenticate transactions with push notification and Retrieve a user.