FAQ: Can the Application Names in Login by Application Be Changed?

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Hybrid
  • Version Affected: 19.07+

     

    Overview

    The New Experience Dashboard's Login by Application section shows a login count for each application/realm. Can the displayed application names be changed?
     

    Answer

    Yes. The name shown in Login by Application is taken from the realm's Log Instance ID, found on that realm's Logs tab. By default, each new realm has a Log Instance ID matching its realm name (for example, SecureAuth4), which is why realms display by their default name in the Login by Application section — this can be time-consuming to map back to what each realm is actually used for.

    Realm's Logs tab showing the default Log Instance ID field set to SecureAuth4.

    Changing the Log Instance ID changes what is shown for future logins to that realm. For example, changing it to a descriptive name like "Global QR Code Enrollment":

    Realm's Logs tab with the Log Instance ID field changed from SecureAuth4 to Global QR Code Enrollment.

    results in the Login by Application section showing that name instead:

    Login by Application section on the New Experience Dashboard, now showing Global QR Code Enrollment as an entry instead of the realm's default name.

     

    Special Considerations

    Changing the Log Instance ID also affects entries logged into some IdP log files, such as the Audit Logs.

    This change is not retroactive. If logins to a realm have already occurred before the Log Instance ID is changed, the Login by Application section continues to show those earlier logins under the original name, alongside a separate entry for the new name going forward.

     

    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.