Skip to content

Align SOCA 0.3.0 with shared identity and browser security requirements - #12

Open
OllieJC wants to merge 1 commit into
mainfrom
codex/shared-requirements-review
Open

OllieJC wants to merge 1 commit into
mainfrom
codex/shared-requirements-review

Conversation

@OllieJC

@OllieJC OllieJC commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

SOCA 0.2.0 selects accounts by verified email and binds callbacks only to the User-Agent. This change requires a separate browser secret and an approved issuer/subject association, closing copied-callback and email-only account-selection gaps.

Reviewed against shared requirements revision 60ea4db. docs/REQUIREMENTS.md records all 34 statuses, source digest, evidence, limits and remaining gaps.

Changes

  • Secure per-transaction browser cookies with encrypted, atomically consumed WordPress state; parallel tabs and copied-callback refusal.
  • Encrypted issuer/subject links, administrator approval/revocation, actor/target audits, revocation tombstones, session invalidation and provisioning rollback on link-write failure.
  • Candidate test-login activation gate, preserved operator sessions, stale-edit rejection and emergency/deactivation invalidation.
  • Complete supported settings through deployment overrides, GUI locks and WP-CLI JSON configuration; one-use operator test URLs and idempotent configuration writes.
  • Wildcard domain admission, WordPress branding/privacy defaults, metadata overrides and deterministic proxy payload/URL limits.
  • Unreleased 0.3.0 version and migration/configuration documentation.

Migration and limits

Existing users require administrator-approved issuer/subject links and a fresh candidate test before SSO rollout. Preserve local administrator access. Existing 0.2.0 settings/keys and WordPress sessions remain. This PR does not publish a release.

This increment does not complete every shared target. Multiple providers, full algorithm support, claim mapping/inspection, provider logout and restore-safe revocation remain tracked gaps. Inline key-set changes require another admitted test and explicit recovery if pairwise subjects change. Provisioning uses compensation rather than a database transaction. Live RESOAuth login and a current complete self-hosted browser login remain unverified.

Validation

31 protocol groups pass on PHP 8.1/8.3/8.5; 23 WordPress groups, two deployment checks, one emergency check, 22 Chromium scenarios, three concurrency scenarios and seven multisite groups pass. Psalm, WordPressCS and local Semgrep checks pass; Composer audit reports no known advisories. Syntax, release metadata, requirement IDs/Markdown links, repeated deterministic ZIP builds and archive checks pass. Tests used isolated disposable WordPress 7.1.3/PHP 8.3/MariaDB 11.4 installations with synthetic providers. Reproduction and evidence limits are in docs/TESTING.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant