Key.file Not Updating After Initial Troubleshooting

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


    The key.file still isn't updating after going through the initial troubleshooting steps. This guide is to be used after performing the initial troubleshooting steps in the guide below.


    The application pools need to be recycled.


    After performing the troubleshooting steps in the guide listed above, perform an iisreset.

    The application pools likely need to recycle, and they aren't. After the iisreset, hit a realm and then check the key.file. By default, the IdP recycles the application pool every 29 hours. (1740 minutes.)

    For reference, the key.file is basically a string that contains the license info, subscription info (what they're paying for), etc. It communicates their certificate against our cloud, and the value in the file is what our cloud returned back.

    0 out of 0 found this helpful



    Please sign in to leave a comment.