How to change the background image in the SA IdP theme

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Hybrid
  • Version Affected:  [23.07-24.04]

    Description:  

    When using the SA IdP theme, if there is a need to change the background image to a custom image, this article will cover the steps needed to do so.

     

    Resolution:  

    24.04 (no Release Update applied):
    In the MFAStyleSheet.css file, located in D:\Secureauth\SecureAuthXX\Themes\SA IdP, you will need to edit the body on line 474, by adding in the following:

     
    background: url("/SecureAuth6/images/test.jpg") no-repeat center center fixed;
    background-size: cover;

     
     
    So the body will look like this:
     
    body {
    background: url("/SecureAuth6/images/test.jpg") no-repeat center center fixed;
    background-size: cover;
    width: 100% !important;
    min-height: 100vh;
    display: flex;
    flex-direction: column;
    justify-content: center;
    background-color: #002B58;
    }

     

     

    24.04 (Release Updates applied):

    In the MFAStyleSheet.css file, located in D:\Secureauth\SecureAuthXX\Themes\SA IdP, you will need to edit the post-auth-view on line 1247 to look like this

    .post-auth-view {

      background: url("/SecureAuthXX/images/test.jpg") no-repeat center center fixed;

      background-size: cover;

      width: 100% !important;

      min-height: 100vh;

      display: flex;

      flex-direction: column;

      justify-content: center;

    }

     

     

    Special Considerations (optional as needed):  

    You will need to modify the url to the path of the realm where the image exists in. Additionally, the background image will need to be placed in:
     
    D:\Secureauth\SecureAuthXX\Images

     

    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.