---
id: TST-PFM-SEC-091
title: Authorizer portal contact 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/authorizer-portal-contact.integration.spec.js
implements:
  - ATS-PFM-SEC-020-08
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/authorizer-portal-contact.integration.spec.js#the
      authorizer signs a portal user’s linked contact (`cid`)
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js#carries
      no `cid` for a portal user not linked to a contact
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js#carries
      the linked contact as `cid`, read from the user’s row under the deployed role
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js#signs
      a changed link, and then a cleared one, on the very next run
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js#carries
      no `cid` for a console user, who is nobody’s contact
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls Cognito, the signing key, registry reads at the declared seams; those
  collaborators remain outside its live proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/authorizer-portal-contact.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - Cognito
    - the signing key
    - registry reads
---
# Authorizer portal contact 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 authorizer portal contact.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## 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 controls Cognito, the signing key, registry reads at the declared seams; those collaborators remain outside its live proof.

## 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.