Troubleshooting: FileSync Does Not Copy Certain Files to the Secondary Server

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

    Overview

    After setting up FileSync, the secondary IdP is missing a file that exists on the primary IdP — for example, a customized company logo image or another realm-specific file.

     

    Cause

    By default, FileSync only copies the minimum files a realm needs to work, such as web.config. It reads what to copy from a file named paths.list, and it only reads paths.list from the SecureAuth0 realm, regardless of which realm it's currently copying.

     

    Resolution

    If your FileSync version is 4.x or newer, perform these steps on the Primary server. If it's 3.x, perform them on the Secondary server instead.

    1. Navigate to D:\SecureAuth\SecureAuth0\.
    2. Back up paths.list.
    3. Edit paths.list to add the path to the file you want copied. For example, if your company logo is companylogo.jpg in the realm's images folder, add:
      <path name="images\companylogo.jpg" />
      The paths.list file open in Notepad, listing web.config, several Resource\Language_XX.resx files, bin\MFA.SecureAuth.Resource.dll, and a new images\companylogo.jpg entry.
    4. Save the file and restart the SecureAuth FileSync service.



     

    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.