Troubleshooting: EULA Link Still Displays on the Login Page With No EULA Value Configured

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All
     
     

    Overview

    Even after confirming a realm's EULA field on the Overview tab is empty, and that the masterpage_eula field under Content and Localization has no value, an end-user license agreement (EULA) link can still appear on that realm's login page.

    Realm login page showing a EULA link below the Restart Login link, beneath the Submit button.

     

    Cause

    The EULA link is rendered by code in the theme's Master.vb file, independent of the EULA and masterpage_eula field values.

     

    Resolution:

    1. In File Explorer, navigate to D:\SecureAuth\SecureAuthXX\Themes\2019 (substituting the applicable theme name if it isn't 2019).
    2. Open the theme's Master.vb file (e.g. SecureAuth2019.Master.vb) and locate the two lines referencing EULALinkButton.
    3. Comment out both lines with a leading single quote.

    Master.vb file open in a text editor with the two EULALinkButton.Text and EULALinkButton.OnClientClick lines highlighted, each commented out with a leading single quote.

    1. Save the file, then click Restart Login on the realm to apply the change.

    If the same issue occurs on another theme besides 2019, follow the same steps against that theme's Master.vb file.


     

    Special Considerations

    If there is more than one IdP server in the environment, repeat this change on each server — FileSync does not copy theme files by default. If more than one realm on the affected theme shows the same issue, copy the edited Master.vb file to each of those realms as well.


     

    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.