1.18 System Configuration on server for Application

This topic provides information on System Configuration on server for Application.

  1. Update below configurations for IOS Push notifications from web console using super admin login.

    Table 1-13 Configurations for IOS Push notifications

    Name Path for the config Value
    Apple Push Notification Key Store Entity -> Event Management Database. (Do not change this)
    Apple Push Notification Service Key Entity -> Event Management <APNS key generated on apple Developer console>
    Apple Push Notification Certificate Type Entity -> Event Management Set it to Development for dev-based key.

    Set it to Production for prod-based key.
    Apple Push Notification Team Identifier Entity -> Event Management Bank’s Team Identifier on Apple Developer Console
    Apple Push Notification Key Certificate Store Entity -> Event Management Database. (Do not change this)
    Apple Push Notification Key Certificate Entity -> Event Management Based 64 of the APNS key certificate generated from Apple Developer Console.
    Apple Push Notification Bundle Identifier Entity -> Event Management Bank’s Bundle Identifier for the application on Apple Developer. This is same as set for Zigbank target in the IOS workspace.
    Proxy settings Entity -> Event Management Proxy settings to allow APNS connection from OBDX server. The format is: HTTP,<proxy>,<proxy port>
    Allowed Push Registration Count Global Settings - >General In base, it is configured as 1. Set to 1 or more than 1 according to bank’s requirement to allow those many devices for push per user.
  2. Update below configurations for Passkey from web console using super admin login.

    Table 1-14 Configurations for Passkey

    Name Path for the config Value
    Relying Party ID for Passkey Entity -> Security Management System Add the domain on which Passkey is to be validated.

    Note: Relying partId is the domain name of the website to which credentials will be associated. (Eg google.com, example.com etc)

    Application connection host Global Settings ->General Host IP of the OBDX MS
    Application connection port Global Settings ->General Host Port of the OBDX MS
  3. Expiry Time Settings

    Table 1-15 Expiry Time Settings

    Name Path for the config Value
    Snapshot Token Expiration Time Global Settings -> Framework It is the expiration time of the token generated for snapshot in mobile application.
    Mobile Application Biometric Token Expiration Time Global Settings -> Framework It is the expiration time of the token generated for biometric token in mobile application.
    Wearable Application Token Expiration Time Global Settings -> Framework It is the expiration time of the token generated for wearable in mobile application.
    Siri and Chatbot Token Expiration Time Global Settings -> Framework It is the expiration time of the token generated for SIRI and chatbot token in mobile application.
  4. Chatbot Settings

    Table 1-16 Chatbot Settings

    Name Path for the config Value
    Chatbot Authentication Type Global Settings -> Security Management System LOCAL/R_SOFT/T_SOFT/PIN
  5. Biometric Settings

    Table 1-17 Biometric Settings

    Name Path for the config Value
    Allowed Device Count for Biometric Registration Global Settings -> Framework Set to 1 or 100 based on bank’s requirement to allow number of devices or biometric registration
       
  6. Soft token Authentication Settings

    Table 1-18 Soft token Authentication Settings

    Name Path for the config Value
    Allowed Window Size for TOTP Token Global Settings -> Framework Base value is 6, Recommended is 6 or 4. Based on these settings the window size of the generated tokens will vary.

Parent topic: OBDX Servicing Application