Unable to register with the Identity Provider (Android)

Unable to register with the Identity Provider (Android)

Created by: John Solis

 

Date Happened: July 16, 2020

 

Component: TVS

 

Platform: Android

 

Root Cause:

  1. On Android’s Entrust ST: Unable to register with the Identity Provider. You will not receive transaction notification



Findings:
  1. Failed to activate mobile soft token through IDG admin portal with Entrust ST passing through external load balancer



Resolution:
  1. Changed port from 8445 to 443 as it was the port defined on the load balancer.

    • Related Articles

    • Could not connect to Provider Address (Android) and Unable to download provider images (IOS)

      Created by: John Solis   Date Happened: July 10, 2020 Component: TVS  Platform: Linux Root Cause: On Android’s Entrust ST: Could not connect to Provider Address. Check your provider address and try again. On IOS Entrust ST: Unable to download ...

    • Cannot Support Unsecured Device (user's mobile soft token application)

      Created by: John Solis   Date Happened: August 13, 2020   Component: Soft Token   Platform: Android/IOS   Root Cause: Can't support unsecured device pop out to the user's mobile soft token application Findings: After the user downloaded the MST and ...

    • Error: Page Cannot be Displayed (Entrust IdentityGuard ISAPI)

      Created By: John Solis Date Happened: N/A Component: N/A Platform: Windows  Root Cause: After entering second factor credentials using the Entrust IdentityGuard ISAPI filter, a “Page cannot be displayed” error is presented                          to ...

    • Soft Token Vulnerability

      Created by: John Solis   Date Happened: August 13, 2020 Component: Soft Token   Platform: Android/IOS Root Cause: Soft Token Vulnerability - 2 TOTPs are valid at the same time. Findings: AUB raised a concern regarding what they called "Vulnerability" ...

    • Delay OTP response

      The client is using OTP as second factor authenticator. They've encountered delay in response on the OTP. Caused: Basically it is Network Provider Issue (Globe) Resolution: To activate the Soft Token OTP for the user.