---
id: TST-PFM-SEC-149
title: Identity link sessions database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#security
      persistence: identity_link_sessions
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#createLinkSession
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#records
      the user, the pool, what the session is for and what makes it believable, with only the
      nonce’s hash
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#names
      the account a provider is being added to when there is one, and none while accepting an
      invitation
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#refuses
      a second session carrying the same nonce, and a user or a pool that is not there
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#the
      reads
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#finds
      a session by its id and by the hash of the presented state, live or not
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#lists
      the live sessions of one user in one pool, newest first, and leaves out the expired and the
      spent
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#findLiveLinkSessionForEmail
      (what the pre-sign-up trigger asks)
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#answers
      the live session and the user it proves, within the trigger’s own pool
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#matches
      the e-mail without regard to case, because the column is citext
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#is
      blind to a session of another pool, which is what keeps a wall from reaching into another
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#answers
      nothing for an expired session, a spent one, and an e-mail nobody in the pool holds
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#consumeLinkSession
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#spends
      the session once, recording the outcome, and refuses the replay
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#records
      why a link was refused, in the API’s own words
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js#refuses
      to consume an expired session and one that is not there, leaving the row untouched
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite’s own dependency setup determines which external collaborators are controlled;
  registration alone does not certify them as live.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  The file has no scenario binding established by this examination. Its executable checks remain
  registered without assigning them broader acceptance coverage.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/persistence/identity-link-sessions.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Identity link sessions database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for identity link sessions.

## What This Suite Proves

The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.