Secret Server Cloud: Errors when accessing secrets

Incident Overview

On October 2, 2025, a subset of customers could not access secrets within their tenant. When they tried to access secret’s general tab, they saw an error message like "s.getTime is not a function." This impacted only active directory secrets linked to discovered accounts with a populated AD expiration date field.  Other secret types, and active directory secrets without a populated AD expiration date field were not impacted.  

‌

Start Time: October 2, 2025, 02:30 PM EDT  

End Time: October 2, 2025, 04:55 PM EDT  

Root Cause

A bug was introduced in the latest Secret Server Cloud release. We reverted the release to restore the functionality for the impacted secrets. The issue occurred because the system misread the expiration date field on Active Directory secrets. In some cases, the system expected the field to always be stored in one format, but in reality, it could appear in different formats. When an expiration date was present, this mismatch caused the error and prevented access.

Preventive Actions

To prevent recurrence, the following actions are planned or in progress:  

Fix how the system reads and processes the expiration date field, so it works reliably in all cases.    

Update internal checks so similar mismatches in field formats are caught before release.