Customers deploying Cloudmersive Private Cloud can leverage Cached Offline API Key Autentication Fallback to ensure uptime in the event that the server cannot connect to the Internet and/or both the Cloudmersive Primary and Secondary High Availability authentication service endpoints are unreachable or unresponsive. This can help to ensure high availability even in the event of arbitrary network partition or reachability issues.

Behavior

If this setting is enabled, successful (valid) authentication outcomes will be securely cached with a configurable time-to-live (TTL). The default is 24 hours. If both the primary and secondary Cloudmersive authentication service endpoints are unreachable, then the service will use cached successful outcomes as a tertiary fallback. Failed outcomes are not cached by design.

Planning

• We recommend making these changes in your lower environments first, and then working your way up to Production.

Enable Cached Offline API Key Authentication Fallback

• First, the customer should update their Cloudmersive Private Cloud server(s) to the latest version.

• Then, the customer should log into the Cloudmersive Management Portal, click on Private Cloud, then Configure Node, then Configure Authentication. Under API Key Authentication enable the checkbox for Enable Cached Offline API Key Authentication Fallback. Optionally, you can also configure the cache Lifetime (default is 24 hours) in minutes. Longer times will give you more time operating normally in the disconnected state. When done, click Save Changes and then Push Configuration to apply the configuration change immediately.