User validity date write-back settings

By default, user validity dates specified in the Valid From and Valid Through fields while creating Oracle Responsibility Assignment Request overwrite the user validity dates defined in Oracle. You can change this default setting using the WritebackConfig.xml.

uservaliditymodification_WritebackConfig.xml

Configure the xml as :

XML file name and path [InstallPath]\Settings\WritebackConfig.xml
Node <uservaliditymodification>always</uservaliditymodification>
Configuration settings

Set <uservaliditymodification> to

  • Never - The existing validity dates of user accounts in Oracle will always be retained when a Responsibility Assignment request is created.
  • Detect - If the validity dates of user accounts specified in the Responsibility Assignment request are different from the validity dates in IRC, the validity dates from the request will overwrite the validity dates in Oracle.
  • Always - The validity dates of user accounts specified in the Responsibility Assignment request will always overwrite the validity dates of these users in Oracle. If the validity dates are not specified in the request, the default setting in the Valid From field which is the current date and the default value in the Valid Through field which is Never Expires will overwrite the existing validity dates of these user accounts in Oracle
Default The default value is Always. The figure above is an example of changing the default setting ‘Always’ to ‘Detect’.