Skip to content

Identity and privilege boundary rollout

This delivery implements the policies in ADR 0005. Each implementation layer must pass its focused checks before integration. The first release enforces these boundaries from initial deployment.

The RemoveCredentialCutover migration removes the four obsolete cutover tables from existing development databases. Historical migrations remain so those databases can upgrade using the maintenance-window sequence. Drain and stop every old API instance before running the migrator: those builds still query the removed tables. This schema cleanup does not revoke sessions or tokens or change passwords, client secrets, or signing keys.

PR validation explicitly permits removal of identity-boundaries/credential-cutover.openapi.yaml under the amended ADR 0005 decision. The OpenAPI comparison scripts accept an exact contract key with --allow-removed-spec (PowerShell: -AllowRemovedSpec). This exception applies only while that contract is absent; other removals and changes to existing contracts retain their normal checks.

Account linking

An authenticated upstream identity with an email matching an existing local account is rejected instead of automatically linked. The public sign-in failure is generic. Operators can investigate the audited association denial without recording the supplied subject or email in that event.

The identifier-only administrative linking endpoint returns HTTP 403 Problem Details with code Forbidden.UpstreamIdentity.ProofRequired. Management Web no longer offers a form for supplying a provider and subject to link an account. Listing and unlinking existing associations remain available under their existing permissions. Proof-based linking and recovery require a separate workflow; matching email is insufficient proof.

New upstream identities with no email collision can receive ordinary local accounts only when the provider permits JIT provisioning. Disabling provisioning does not disable the provider or remove existing associations. Deploy the provider configuration migration before running the updated API. Existing provider registrations retain the previously effective enabled setting; explicit changes are persisted and enforced thereafter.

Before deploying this layer, identify integrations using identifier-only linking and preserve independently usable login methods for affected users. Restoring email-based linking or the raw-identifier bypass is not a safe rollback. Database uniqueness constraints continue to reject concurrent attempts to claim the same email or provider/subject; a failed attempt must not be treated as an existing-account authentication success.

Management Web deployment preparation

DbMigrator prepares the fixed management-web-client in both the domain application registry and OpenIddict. For an independently reviewed initial deployment, set Seed:AdministrativeAccess:BootstrapManagementWeb=true to create its delegated administrative resource grant. The default is false; client registration alone grants no administrative access. This bootstrap grants no machine permissions and does not give users authority they do not already hold.

Rerunning preparation preserves existing grants, including withdrawn access. An existing client whose status, profile, scopes, redirects, credentials, or PKCE configuration differs from the reviewed deployment configuration causes preparation to fail; reconcile it through the approved administrative workflow before rerunning. Keep the initial bootstrap flag out of ordinary runtime configuration.

Delivery tracking

The checked-in OpenAPI contract marks raw linking as deprecated and describes its proof-required 403 response. The shared administrative client no longer exports linkUserUpstreamIdentity or its request type. This is an intentional breaking security change: remove raw-link calls from integrations; there is no supported replacement until an independent proof workflow is delivered. Identity listing remains supported.

The Admin API contract release is 2.0.0, advancing from 1.1.0 for this removal of the advertised raw-link success response and shared-client operation. Release the API, shared administrative client, and Management Web together under ADR 0003. This contract release does not introduce a versioned URL: /api/admin remains the administrative base path. Consumers must migrate away from raw-link calls before upgrading; the endpoint continues to return the documented proof-required 403.

Implementation issues are #445–#456. Broader assessment findings and formal OpenID Connect certification are separate work. The pre-release credential cutover workflow was removed; see the amended deployment decision in ADR 0005.