Login

Prev Next

The Apex login screen provides a seamless and secure access to all the essential applications. To login to  Apex application, perform the following steps.

Supported Browsers and Versions

Apex can be accessed using multiple browsers and their supported versions.

  • Chrome Version 126.0.6478.56 (Official Build) (64-bit)

  • Microsoft Edge Version 125.0.2535.79 (Official build) (64-bit)

  • Firefox Version 126.0.1 (64-bit)

  • Safari Version 17.5 (19618.2.12.11.6)

Screen Resolution

The optimal settings for Scale and Layout to view the Apex application are as follows:

  • 100% scaling is recommended for (1360×768 to 1680×1050) display resolution.

  • 125% scaling is recommended for 1920×1080 display resolution.

GDPR Mandatory Consent

To strengthen application security and ensure compliance with data protection regulations, the GDPR consent flow has been redesigned. General Data Protection Regulation (GDPR) is a regulation in Europe on data protection and privacy for all individuals within the European Union.

To ensure compliance with GDPR Rules, the Apex application asks for acceptance from end users that following fields will be stored in the Apex application in an encrypted format.

The specific fields for personal data to be stored in encrypted format are:

  • Joining Date, Email-ID, Login ID, Country, Address, Contact Number, Mobile Number, State, City, Pin, and Role.

Users must now explicitly accept the GDPR terms before accessing any application features. For first time users, who login to the application, you need to accept the GDPR consent forms, prior to using the application. Upon acceptance of GDPR, your personal data will be displayed to Analysts and Admin

Summary of Key Changes

✔ Mandatory Consent

  • Users must accept the GDPR terms before any part of the application becomes accessible.

  • Consent is now enforced at the server side, preventing bypass attempts.

✔ Updated UI/UX

  • A redesigned GDPR consent interface has been implemented.

  • The flow prevents hiding or skipping the consent form using browser tools or script manipulation.

✔ Security Compliance Fix

  • Sensitive content is no longer transmitted to the browser before consent.

  • Server-side checks strictly block unauthenticated or non‑consented access.

Log In

To log in to the apex application, perform the following steps:

  1. Enter Apex URL in the address bar of the browser.

  2. Sign In page is displayed.

    Figure: Log in page

    SSO  Error

    If SSO is not configured, then an error is displayed as below.

    Figure: SSO not found

    Reset Password

    To reset your password, perform the following:

    1. Click Forgot Password? hyperlink to reset your password.

      Figure: Forgot Password

    2. An additional field with Reset option is provided.

    3. Enter your login Email Address and click Reset Password to change the password.
      Figure: Reset Password

    4. Upon performing the reset action, a success message is displayed.

      Figure: Reset success message

  3. Sign in to your account by entering Email and Password in the fields.

    Note

    Ensure that you type in the correct Email and Password as provided by your system Administrator. If you type in an incorrect Email or Password, the application displays an error message.

  4. Click Sign In.

  5. If GDPR is enabled, you are redirected to the GDPR Consent Form. Accepting this consent by clicking the ACCEPT & CONTINUE button is considered that you are agreeing to display your personal data to the Administrators of the application. Upon clicking ACCEPT & CONTINUE, a confirmation poup appears.

    Figure: GDPR Consent Form

  6. A confirmation message appears as shown in the following screen.
    Click Ok to continue.

    Figure: Confirmation message

  7. Only after acceptance of GDPR consent, the user is redirected to the application dashboard screen.

    Figure: Dashboard screen after login

  8. If a user declines the GDPR consent and relogs in, the user is displayed the following message indicating that the GDPR consent was previously declined.

    Figure: Previous GDPR Consent Declined