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

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:

  1. On Android’s Entrust ST: Could not connect to Provider Address. Check your provider address and try again.
  2. On IOS Entrust ST: Unable to download provider images.



Findings:
  1. Soft token activation is successful. However, it takes a lot of time and the customization settings were not pulled



Resolution:
  1. Changed the address of the localized branding logo to external-facing.
  1. The error occurred because Entrust ST (mobile application) cannot pull the images from the internal IDG server. 

    • Related Articles

    • Unable to register with the Identity Provider (Android)

      Created by: John Solis   Date Happened: July 16, 2020   Component: TVS   Platform: Android   Root Cause: On Android’s Entrust ST: Unable to register with the Identity Provider. You will not receive transaction notification Findings: Failed 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" ...

    • 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 ...

    • Error Code (2500) Failed to Connect to Any of the Configured URLs

      Created By: John Solis Date Happened: N/A Component: N/A Platform: Linux Root Cause: Error code (2500) failed to connect to any of the configured URLs Findings:  Possible Cause #1 The attempt to connect to the directory or database timed out. ...