How to increase the allowed clock skew for API calls

Version Affected:  All

Description:  

We have a default clock skew of 1 minute for calls to the Authentication API. 

This should be sufficient and we don't recommend increasing it. 

Instead, all the servers should be using NTP to keep them in sync. 

This document shows you how to increase the allowed clock skew for those exceptional circumstances where NTP is not possible

Cause:  

Our API has a 1 minute tolerance for time drift by default

Resolution:  

1. Take a backup of the current web.config for the realm in question

2. Go to Advanced Settings in the Admin Console

3. Click Tools | Decrypt Web.Config and decrypt the appropriate realm

4. Edit the web.config to add the following AppSetting to the <AppSettings> section

5. <add key="Api.HttpRequestValidityPeriodInMinutes" value="2" />

6. Save the web.config

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.