FileSync does not make exact replicas of folder names during sync

Follow
    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Hybrid
  • On Premises
  • Version Affected:  FileSync 4.0.13 and lower

    Description:  

    Folder names on the replicas will all be lower-case characters and not have the same SecureAuth# name as the master server. If integrations for SAML/OIDC/WS-Fed require the URL to be a specific case, this may cause issues with your integration.

     

    Cause:  

    Microsoft is a case-insensitive operating system, service providers may be using case-sensitive server technology, and, currently, FileSync does not match the case of each character in the folder name during replication.

     

    Resolution:  

    To resolve this issue follow the below:

    1. Make a backup copy of the IIS configuration file (C:\Windows\System32\inetsrv\config\applicationHost.config)
    2. Open the original file in a text editor and replace path="/secureauth with path="/SecureAuth 
    3. Save the file

     IIS will pick up the changes automatically and refresh properly.

     

    *The case of the text will have to match how the SAML/WS-Fed URL's are setup in the service provider's configuration. Also note, the above changes may be required on multiple servers depending on the number of servers being used in the FileSync configuration.

     

    Special Considerations:  

    An alternative method to resolve this issue which also addresses the filesystem folders can be found here:

    https://support.secureauth.com/hc/en-us/articles/360045169611-How-to-restore-the-correct-case-for-Realm-folders-and-IIS-Apps

     

     

    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.