Internal GCCAP operating surface

This page is retained behind the public client website.

GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.

Open portal access

Internal GCCAP surface

Prepare GCCAP users, portals and command access for production identity.

The Identity Lab is the internal Internal system phase surface for managing identity provider readiness, MFA requirements, session hardening, role boundaries, user lifecycle controls and access reviews before real client onboarding scales.

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
ScopeIdentity + access
AccessAdmin-only
OutputReadiness + blockers

Operational layer

Identity Lab API surfaces

Use admin-gated endpoints to inspect and update identity readiness.

/api/identity/stats

Current Build 17 identity summary and production blockers.

/api/identity/providers

Local pilot, production OIDC and enterprise SSO provider readiness register.

/api/identity/mfa

MFA requirements for admin, command and client roles.

/api/identity/readiness

Production identity readiness scan with high/critical blockers.

Operational layer

Controlled boundary

Build 17 is intentionally a foundation, not a final SSO deployment.

No fake SSO

The lab reports missing provider credentials rather than pretending SSO is connected.

No secrets in ZIP

Session, admin, ingest and identity secrets remain environment variables or future managed secret-store entries.

Pilot safe

Local user flows remain acceptable for controlled pilot testing only.

Production path

Build 18 onward can add deployment, observability and identity provider integration hardening.