13 rotation providers, reusable policies with retry logic, and infrastructure credential rotation -- from LDAP to cloud IAM keys.
See It In Action
47 secrets checked. 3 rotated. 0 failed.
From policy definition to scheduled rotation, the entire lifecycle is automated and audited.
Define a reusable rotation policy with a schedule (daily, weekly, custom cron), rotation provider, max retries, and retry delay. Policies are shared across multiple secrets.
Link any number of secrets to the policy. Each secret specifies the rotation provider (PostgreSQL, LDAP, AWS IAM, etc.) and any provider-specific credentials needed to execute the rotation.
The rotation scheduler fires on the policy schedule, executes the provider-specific rotation, writes the new value as a new secret version, and retries on failure with configurable backoff.
One scheduler. 13 providers. Every credential refreshed on time.
Cron or Interval
13 Providers
PostgreSQL, LDAP, AWS, Azure, and more
Versioned Secret
Previous version retained for rollback
Zero Downtime
Apps get fresh credentials on next request
Reusable policies, provider-specific logic, and retry handling -- all in one place.
Define a rotation policy once and attach it to any number of secrets. Change the schedule in one place and all attached secrets update. No per-secret configuration drift.
Configure max retries and retry delay per policy. Failed rotations are retried with the configured backoff. Persistent failures trigger alerts and are visible in the rotation status dashboard.
Rotate LDAP service account passwords via the unicodePwd LDAP extended operation. Works with on-premises Active Directory and cloud-synced directory services without domain admin rights.
Rotate PostgreSQL credentials without a superuser account. The provider uses ALTER USER CURRENT_USER so the rotating user changes their own password -- no elevated database permissions required.
CoreLink writes the rotated credential as a new secret version rather than overwriting the existing one. Applications fetching the secret receive the latest version. The previous version is retained for rollback if a rotation causes an outage.
Every rotation event is written to the hash-chained audit log -- which provider ran, whether it succeeded or failed, and the new version number. Rotation status is visible in the dashboard in real time.
Connect CoreLink to your databases, directories, and cloud IAM -- and let the rotation scheduler handle credential hygiene across your entire estate.