SecureAuth version affected: All
After setting up FileSync, it's discovered that the secondary IdP does not display the Company Logo that was set on the Primary IdP.
By default, FileSync only copies the minimum amount necessary for the Realm to work. Such as the Web.Config
It reads what to copy from a file called paths.list
It only reads paths.list from SecureAuth0 no matter which realm it is copying..
If your filesync version is 4.x and newer, perform these steps on the primary. If it's 3.x, perform them on the Secondary server,
1. Navigate to D:\SecureAuth\SecureAuth0\
2. Take a backup of paths.list
3. Edit paths.list to include the path to the file you want to copy.
For example, if you've used a companylogo called companylogo.jpg this is stored in the images folder so the extra entry would appear as
<path name="images\companylogo.jpg" />
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
Is there any limitation to the Path and/or Files that can be included in paths.list file?
For example, we are working tailoring team to upgrade our 9.0.2 customizations to 20.06, in this effort, they have provided customized pages in locations like UserControls\2019\Customized\*.ascx. Could we have those files sync also?
As long as it in the SecureAuth Realm folder, there shouldn't be a limitation to what you can sync. Just keep in mind that syncing more files or folders would cause filesync to take longer to complete.
Please sign in to leave a comment.