I am currently working on disabling a GRC account using the OOTB GRC connector. While the account is successfully being disabled, I’ve noticed that the “Valid From” attribute is being updated to the current date, rather than retaining the existing date already present in the account attribute.
I’ve attempted to set the attribute through the Before Provisioning Rule, but unfortunately, that did not resolve the issue. Please provide any sample rule which I can use to validate against the rule that I have in place!
Could you kindly advise if there are any known configuration changes required on the GRC side to address this behavior? Additionally, any relevant documentation or insights on handling this scenario would be greatly appreciated.
In my case also same things happened i think
The “Valid From” date for SAP GRC attributes often defaults to the current date. This behavior is typically due to the way the integration is configured between SailPoint and SAP GRC. When a new attribute or user is synchronized, the system sets the “Valid From” date to the current date to indicate the start of the validity period for that attribute or user in the system.
Hi @Abhishek_1995 ,
Thank you for the response. As this is a termination scenario, the expectation is to pass the account attribute value instead of the current date, as this might cause issues/ Errors if the “Valid To” date is in the past.
Let me know if there is a way we can overcome this and pass on the ValidFrom account attribute value instead of current date !
I want to update both, while the Valid To is being set to current date, the Valid From is also being set to the current date , making both the attributes with same value!
Could you clarify your requirement? In your previous response, you mentioned setting the valid from attribute to its existing value. However, you also said that both valid to and valid from should be set to the current date. I’m a bit confused. Could you please explain further?
You can update the Valid To date to the current date or future date but not the past date. If you try to update the past date to the Valid To date exception may occur.
If both date is updating with same value you ask with SAP team whether both date are in sync.