Bug: FileSync Does Not Create Vanity-Named Realms on Secondary Servers

Version Affected: 24.04
Bug Number: N/A
Bug Status: Closed - Fixed
Fixed in Version(s): FileSync 4.5.1.8 or later

 

Overview

FileSync does not successfully create a realm on a secondary server when that realm has been given a custom ("vanity") name instead of the default SecureAuth# naming pattern.

 

Cause

Realms can be given a custom name in Internet Information Services (IIS) rather than using the default SecureAuth# naming pattern. FileSync expects every realm to use the standard SecureAuth# naming format, so it does not recognize a custom-named realm and fails to create it on secondary servers.

 

Resolution / Workaround

Upgrade to FileSync 4.5.1.8 or later to resolve this issue.


 

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.