Troubleshooting: 2016 Light Theme Submit Button Not Working on Mobile Devices

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: the version range differs by cause, noted individually below.
     
     

    Overview

    When a realm that uses the 2016 Light theme is accessed from a mobile device, the Submit button does not work. There are two independent causes, one for iOS and one for Android:

    • See Cause 1 - On iOS, this is a known product defect.
    • See Cause 2 - On Android, this is caused by a specific realm setting.

    These causes are not related, so a fix for one will not resolve the other.

     

    In this article


     

    Cause 1: Product defect on iOS (EE-671)

    Applies to versions 8.2 through 9.1.

    This is a known product defect, tracked as EE-671, and is fixed in Identity Platform version 9.2.

     

    Resolution 1:

    To resolve this, upgrade to Identity Platform 9.2 or later. As a workaround if you cannot upgrade immediately, use a theme other than 2016 Light.


     

    Cause 2: Client Side Control setting on Android

    Applies to version 8.2 and later.

    On Android, this is caused by the Client Side Control setting on the realm's Workflow tab being set to either Universal Browser Credential or Java Applet, as shown below.

    Workflow tab showing the Client Side Control setting set to Universal Browser Credential, which causes the Submit button issue on Android.

     

    Resolution 2:

    To resolve this:

    1. Open the Admin Console.
    2. Navigate to the Workflow tab of the realm.
    3. Set Client Side Control to either Browser Plugin or Device Fingerprint, as shown below.

    Workflow tab showing the Client Side Control setting changed to Device Fingerprint, resolving the Submit button issue on Android.




    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.