User Authentication

Name: HID_IS_FETCH_USER_ATTRIBUTES (Default value: false)

Description: This property controls the behavior of the identity provider service.

• If the identity provider service is set to DbxUserLogin (Custom Identity): Set this property to true.

• If the identity provider service is set to customHIDLogin (default): This property can be left as false (default value).

To validate the endpoints, log in to the Fabric Console and execute the HIDIdentityService/login integration service:

1. Open Fabric and select the Environments option from the left menu.

   

2. Select the App Services option.

   

3. Select Integration Services, search for HIDIdentityService, and select the login operation from the Select Options drop-down menu.

   

4. The following page will be displayed, allowing you to enter parameter values and receive a response.

   

   Parameters values to be passed:

   • Payload:

     Copy

     Payload: (update your payloads accordingly)

     {
     "Meta": {
     "EventType": "urn:com:temenos:security:event:login:v1",
     "RiskScore": {
     "Required": "0",
     "Current": "0"
     },
     "TransactionId": "9090"
     },
     "urn:com:temenos:security:event:login:v1": {
     "Scope": "LOGIN",
     "Name": "Temenos Internet Banking",
     "userid": "UpdateUsenameHere",
     "password": "UpdatePasswordValueHere"
     }
     }

     Note:

     Update only the userid and password values within the payload.

     • userid: This value is the same as username.

     • password: This value is your password/secure OTP used for first-factor authentication.

   • isMFA: The value indicates whether your application supports multi-factor authentication (true) or single-factor authentication (false).

   • authType: It is dependent on the first factor of authentication.

     • For static password: STATIC_PWD

     • For secure code: SECURE_CODE

     • For OOB PIN: OTP_SMS_PIN

5. A successful response from the API would look as below with isMFA is set to true.

   

6. A successful response from the API would look as below with isMFA is set to false.

   

1. In the Fabric console, navigate to Integration Services and search for the getCustomerIdentityAttributes operation within dbpProductServices.

   

2. You will be able to see the below page where you can add parameter values and get a response.

   

   Note:

   • userName must exist in the Infinity database.

   • Since the API uses anonymous app user security, include x-kony-app-key and x-kony-app-secret in the header.

Set these keys only if they haven't been set for HID Global services previously.

1. Select the app where you have the HID Global services available, and select the Publish tab.

2. Within the Server properties section, enter the App Key and App Secret values.

Use the Primary App Key and Primary App Secret for this configuration.

1. Export the DbxUserLogin identity service from Fabric.

   

2. Extract the DbxUserLogin(v1.0).zip and you will find the services folder at the top level, as shown in the below image.

   

3. Open the Meta.json file (from location: ../Services/_Identity/DbxUserLogin/Meta.json) in the text editor and remove the subtype key and the corresponding value from the config object.

   

4. Inside the config object, add a new property named mfa_url.

5. Set the value of mfa_url to the Second-factor endpoint of the CustomHIDLogin identity service.

6. Modify the custom_idp_url property to point to the First-factor endpoint of the CustomHIDLogin identity service.

   Copy

   Before Changes

   {
     "name" : "DbxUserLogin",
     "displayName" : "DbxUserLogin",
     "type" : "custom",
     "version" : "1.0",
     "metaPreference" : -1,
     "config" : "{
                  \"pre_mfa_token_timeout\":10,
                  \"header_params\":[\"x-kony-integrity\"],
                  \"session_restrictions\":{\"session_restriction_type\":\"allow_any_number_of_sessions\"},
                  \"sub_type\":\"customer360\",
                  \"is_mfa_enabled\":true,
                  \"provider_params\":{},
                  \"body_params\":{},
                  \"custom_idp_url\":\"https://abc.domain.com /services/DbxCustomerLogin \"
                  }",
     "policyConfig" : "{\"def_user_status\":\"pending\",\"max_login_fail\":5}",
     "admissionPolicy" : "no_approval_needed",
     "identityMeta" : {
       "allow_sso" : false
     },
     "isIntegrityEnabled" : true,
     "ssoenabled" : false,
     "empty" : true
   }

   Copy

   After Changes

   {
     "name" : "DbxUserLogin",
   "displayName" : "DbxUserLogin",
     "type" : "custom",
     "version" : "1.0",
     "metaPreference" : -1,
     "config" : "{
                  \"pre_mfa_token_timeout\":10,
                  \"header_params\":[\"x-kony-integrity\"],
                  \"mfa_url\":\" https://abc.domain.com/services/HIDIdentityService\SecondFactorlogin",
                  \"session_restrictions\":{\"session_restriction_type\":\"allow_any_number_of_sessions\"},
                  \"is_mfa_enabled\":true,
                  \"tracking_attribute\":\"no_tracking\",
                  \"provider_params\":{},
                  \"body_params\":{},
                  \"custom_idp_url\":\"https://abc.domain.com /services/HIDIdentityService \"
                  }",
     "policyConfig" : "{\"def_user_status\":\"pending\",\"max_login_fail\":5}",
     "admissionPolicy" : "no_approval_needed",
     "identityMeta" : {
       "allow_sso" : false
     },
     "isIntegrityEnabled" : true,
     "ssoenabled" : false,
     "empty" : true
   }

7. Save the changes, zip the Services folder, and rename it as DbxUserLogin(v1.0).zip.

8. Go to API Management in your fabric and import the updated service Zip file.

   If you check the DbxUserLogin service after the successful import, you will be able to observe that the type of the service has changed to Custom.

1. Open the Fabric app where DbxUserLogin Identity service is present.

2. Go to Publish Tab.

3. Click the Configure and Publish option below.

4. Expand the Service configuration and expand the Identity service configuration.

5. Update the custom idp URL with the First-factor endpoint of the DbxUserLogin.