Skip to main content

Double Blinded

This page describes the Double Blinded Login Init and Verify method of Authentication.

The Double Blinded Login (DBL) method is the default method of user identification and verification within the HaaS environment.

The DBL method involves two key steps:

  1. Init Login: In this step the Username (username) is accepted via the Data Adapter and a unique Request Identifier (requestId) is returned. No other information is disclosed at this stage.
  2. Verify Login: In this step the OTP (otp) submitted by the Consumer and the previously obtained Request Identifier (requestId) are submitted. The API call returns a list of Principal Identifiers (principalIds) and a single userId.

In addition, the Get User Notification Information endpoint is required to achieve Biza Dashboard and Notification requirements.

Advantages​

  • The actual Principal Identifiers are blinded from the HaaS environment until the user (and therefore HaaS) successfully validate an OTP.
  • Existing mechanisms for OTPs can be utilised via customer specific channels.

Disadvantages​

  • Higher implementation effort as the Customer is responsible for implementation.
  • Currently, no explicit method of returning Ineligible Block information. This is a deliberate design decision to protect this method from enumeration attacks but means that the method for presentation is limited to a consent flow that simply states "No Eligible Accounts".
  • Means that HaaS Manager administrators must know the User IDs and Principal IDs to operate HaaS Manager rather than being able to lookup Users and Principals by their login attributes.

High Level UML Diagram​

Endpoint Specific Guidance​

  • To combat enumeration attacks, the Init Login call SHOULD succeed even if the username provided is invalid.
  • The Verify Login call SHOULD NOT succeed unless the OTP is correctly verified. This includes situations where the original username is invalid.
  • The otp field in the Init Login response must only be provided for test installs (if at all) and represents a way of conducting testing without actual delivery of the OTP.
  • While the examples for requestId use a UUID it is a string of no specified length (although less than 500 characters is strongly recommended). This enables implementers to avoid state preservation by instead providing an encrypted payload as the requestId that is then decrypted on receipt in Verify Login.
info

Click here for the data-adapter endpoint configuration.