How do I resolve an authorization failure that results from the clocks of the Access Manager and Policy Agent machines being out of sync?
By configuring the com.sun.identity.policy.client.clockSKew property in the AMConfig.properties file, you can set the allowable time difference between the Access Manager and the 2.2 Policy Agent machines. You should still run the time-syncing service, such as the Network Time Protocol (NTP), and closely synchronize the times. Set clockSkew to handle the minor time difference even if you run NTP. Here is what the related content in the AMConfig.
By configuring the com.sun.identity.policy.client.clockSKew property in the AMConfig.properties file, you can set the allowable time difference between the Access Manager and the 2.2 Policy Agent machines. You should still run the time-syncing service, such as the Network Time Protocol (NTP), and closely synchronize the times. Set clockSkew to handle the minor time difference even if you run NTP.
Related Questions
- When I set the do_sso_only flag to true, the Policy Agent still looks for policies on Access Manager. Can I configure SSO without authorization?
- How do I resolve an authorization failure that results from the clocks of the Access Manager and Policy Agent machines being out of sync?
- Will the failure of a MySQL Cluster Manager agent impact the availability of the MySQL Cluster database?
