Transformation Engine rules are not synchronised to other nodes

Follow

Version Affected:  All

Description:  

Changes made to transformation engine rules on the Primary IdP in a FileSync cluster are not being reflected on secondary nodes within the cluster.

 

Cause:  

The transformation rules are saved in a file that isn't synced by default by Filesync, More info here:
https://support.secureauth.com/hc/en-us/articles/360019887951-FileSync-How-to-Use-What-is-it-How-Does-it-Work-

 

Resolution:  

You resolve this you can either manually make the same changes on the secondary node(s) OR you can change the Filesync configuration to include the Transformation Engine rule file in it's synchronisation by using the following procedure:

1. Stop the FileSync service on the Primary node.

2. Open this file on the primary node in a text editor:
D:\Secureauth\SecureAuth0\paths.list


3. Add the below line to the second from last line so it's just above the </list> tag.  It should look like the below example:

<path name="PostAuthData\usersprofiledata.xslt" />



4. Save the file.

5. Start the FileSync service on the primary node.

 

 

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.