---
id: TST-PFM-INT-527
title: credential lifecycle
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js
implements:
  - ATS-PFM-INT-005-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 3: the previous credential is superseded with its deletion due seven days after the
      replacement and not destroyed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 3: the replacement is active with the hint K3mT and no rotation date, the only active
      credential
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 3: the replacement’s secret has no deletion date and the previous one’s has
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 5: svc_accounting’s payments.authorize right after the replacement, before the re-verification
      runs, leases the new credential
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 7: six days later the maintenance destroys neither key and both secrets still exist
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163
      step 7: eight days later the maintenance destroys the superseded credential, audits it once and
      leaves the active one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 3: the active credential’s deletion is due seven days after the disconnection
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 3: the superseded credential keeps the deletion date its replacement gave it
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 3: the connection still names the replacement credential
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 3: the credential.revoked rows carry the same dates
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 7: six days later the maintenance destroys neither revoked credential and both secrets still
      exist
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0182
      step 7: eight days later the maintenance destroys both revoked credentials and audits
      credential.destroyed twice
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# credential lifecycle

## Verification Boundary

This database and service suite exercises credential lifecycle. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.