Mapping transaction types (such as LOGIN, FUND_TRANSFER) and Mobile OTP authentication
search cancel

Mapping transaction types (such as LOGIN, FUND_TRANSFER) and Mobile OTP authentication

book

Article ID: 442843

calendar_today

Updated On:

Products

CA Advanced Authentication CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort) CA Strong Authentication

Issue/Introduction

Can a mapping be created between transaction types (such as LOGIN, FUND_TRANSFER, etc.) and Mobile OTP authentication for reporting purposes, without making changes to the current profile configuration?

Environment

Symantec Advanced Authentication 9.1.5.x

Resolution

 Below is the scenario where we can distinguish the transaction type:

  1. Create two authentication policies with same configuration parameters (i.e., create a copy of the existing authentication policy for CAMobile OATH OTP), say "aotp_auth_login", "aotp_auth_funds".
  2. During the second factor authentication, middleware application has to set the authentication policy in the request, based on the flow type as the customer application has the knowledge of the type of the txn (for login flow set "aotp_auth_login" as the auth policy, and "aotp_auth_funds" for funds transfer flow.
  3. In the database, we store the authentication policy name in the column "CREDAUTHPOLICYNAME", with which authentication is performed.

Below is the sample request:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:msgs="http://ws.arcot.com/WebFortAuthAPI/7.0/msgs" xmlns:xsd="http://ws.arcot.com/WebFortCommonAPI/7.0/xsd">
  <soap:Header/>
  <soap:Body>
     <msgs:VerifyArcotOTP>
        <msgs:userName>testuser1</msgs:userName>
        <msgs:otp>029373</msgs:otp>

        <msgs:additionalInput>
           <!--Zero or more repetitions:-->
           <xsd:pairs>
              <xsd:name>AR_WF_AUTH_POLICY</xsd:name>
              <!--Optional:-->
              <xsd:value>aotp_auth_login</xsd:value>
           </xsd:pairs>
        </msgs:additionalInput>
     </msgs:VerifyArcotOTP>
  </soap:Body>
</soap:Envelope>