How often is the Key.file updated on the SecureAuth IdP

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version Affected: All



    The D:\SecureAuth\Key.File used for licensing IdP appliances is periodically updated on a rolling period of approximately 60 days.  The logic behind the frequency of updates can be explained.



    When the IdP is in active use by end users the IdP will attempt to update the key.file but not every day. This can give the illusion that the IdP isn't refreshing its license.



    The logic in later versions of IdP (9.0+) is that the debug logs will show the Current Date together with Warn Date, and Expire Date.
    Once the Warn Date is reached the IdP will try to update the key.file.

    Here is an example taken from a log where the warn day has been reached and the IdP tries but fails to update the key.file

    httpmodule.CheckLicense.licensedata.: 10/22/2018 9:50:46 PM || warnday: 10/22/2018 10:57:01 AM || expireday: 11/21/2018 9:57:01 AM
    httpmodule.CheckLicense.utcnow.: 10/22/2018 9:50:46 PM > warnday: 10/22/2018 10:57:01 AM
    Failed to update key file. httpmodule.check.string.empty: 1zRsQ+MBKWPTSMs4ZugjQ3wsMG4TX9VOyKAaaIY8iVB6nbTTvwpOAzva3j4odxmvTjt614vfpMMol2gBRMfQE5qeJos3pEaIQfkWRw0UBD6iBke8H+Cn2EbKA/DjLXoF5ngszF1+3a/q3CS8r4Ks9w==�


    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



    Please sign in to leave a comment.