How To: Create a Vanity URL for an Identity Platform Realm

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

     

    Overview

    This article explains how to create a vanity URL for a SecureAuth Identity Platform realm. By default, realm URLs always follow the format https://fqdn.company.com/SecureAuthXXX (where XXX is the realm number) — a vanity URL lets that same realm also be reached at a friendlier, more memorable URL.

     

    Create a Vanity URL

    Custom Alias' are available within 26.x as part of Identity Provider and New Experience Realms, there is no requirement to follow the below steps.

    A vanity URL is created within Microsoft IIS.

    1. Open IIS Manager on the Identity Platform appliance.
    2. Expand the tree until you see Default Web Site (Server > Sites > Default Web Site).
    3. Right-click Default Web Site and choose Add Application....
    4. For Alias, enter your preferred vanity URL — for example, PasswordReset.
    5. Change Application Pool to .NET v4.5 — this is the default Application Pool used for Identity Platform realms.
    6. Change Physical Path to the full path of the realm the vanity URL should point to — for example, D:\SecureAuth\SecureAuth3.

    IIS Add Application dialog with Alias set to PasswordReset, Application pool set to .NET v4.5, and Physical path set to D:\SecureAuth\SecureAuth3.

    1. Click OK.

    The realm is now reachable at both the new vanity URL and its original URL:

    Two browser tabs showing the identical Password Reset page, one at the original https://localhost/SecureAuth3/ URL and the other at the new vanity https://localhost/PasswordReset/ URL.

     


     

    Special Considerations

    If FileSync is active in the environment, vanity URLs are also copied and created by FileSync — a new vanity URL only needs to be created on the Primary Identity Platform server.


     

    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.