Loading…
Loading documentation...
Set up multi-tenant OIDC SSO, ES256 JWKS, SCIM provisioning, W3C Verified Credentials, ZTNA access and zero-public-IP Cloud Bastion.
Commands checked on 2026-11-12 with SAU Cloud Identity v1.7 (OIDC 1.0, ES256 JWKS, SCIM 2.0), sau CLI 0.2.0.
Your organization will run a complete first-party zero-trust identity and access stack on Servers Are Up: an OIDC 1.0 / OAuth 2.0 Identity Provider with ES256 JWKS signing and SCIM 2.0 directory lifecycle provisioning (/dashboard/identity), Conditional Access, W3C Verifiable Credentials, and Zero-Trust Private Access (ZTNA) policy enforcement (/dashboard/entra-suite), plus zero-public-IP browser SSH and RDP jump sessions via Cloud Bastion (/dashboard/bastion).
/dashboard.cloud:read and cloud:write scopes (Account settings > API keys at /account/api-keys).Open Access > Identity & OIDC (/dashboard/identity):
ES256 JSON Web Key Set (JWKS) URL (/.well-known/openid-configuration via /api/v1/identity).Internal Engineering Portal), and register its exact HTTPS callback URI (https://portal.example.com/api/auth/callback/sau).S256) enforcement and copy the generated client_id and client_secret straight into Access > Key vault & KMS (/dashboard/key-vault).If you also synchronize users and groups from an external HR directory or IdP, generate a scoped SCIM 2.0 bearer token on the SCIM Provisioning tab so joiners, movers, and leavers are provisioned and deprovisioned automatically.
Open Access > Identity governance & ZTNA (/dashboard/entra-suite) to govern who can reach which internal hostname under what device, MFA, and IP risk posture:
ZTNA) application rule mapping an internal destination (such as postgres-admin.internal.sau or grafana.internal.sau) to required MFA assurance and allowed principal groups.sau CLI before cutting over users:# Inspect your Identity Governance, ZTNA, and Verifiable Credentials state
sau entra show
# Evaluate Zero-Trust Access policy against a private destination
sau entra gsa-evaluate "grafana.internal.sau"
ES256) for high-assurance operatorsWhen contractors, hardware enclave operators, or partner organizations need cryptographically verifiable role proofs (VerifiedEmployee, ZeroTrustContractor, HardwareEnclaveOperator, or CustomerKYB), issue a signed W3C Verifiable Credential from /dashboard/entra-suite or the CLI:
sau entra vc-issue "Ada Lovelace (Principal SRE)" --type HardwareEnclaveOperator
Every issued credential carries a verifiable ES256 cryptographic proof and can be revoked instantaneously if a contractor engagement ends.
Instead of opening TCP 22 or 3389 on any virtual machine's public IP:
22 and 3389 closed on Network > Firewall (/dashboard/network?tab=firewall)./dashboard/bastion) (or run sau network bastion-list -o table).JIT) SSH or WebRDP session ticket (for example 60 minutes, tied to a ticket reason such as INC-402 database index tune).# Audit active Cloud Bastion hosts and ephemeral JIT tickets
sau network bastion-list -o table
Verify your OIDC discovery document, ZTNA policy decision, and Bastion session ledger:
curl -fsSL "https://serversareup.com/api/v1/entra-suite" \
-H "Authorization: Bearer sau_your_token_here" | jq '{
ztnaApps: (.privateAccessApps | length),
issuedCredentials: (.verifiableCredentials | length),
ciemFindings: (.ciemFindings | length)
}'
Confirm that direct connections from the public internet to port 22/3389 on your private VM time out, while an authenticated Cloud Bastion JIT session connects in under two seconds.
redirect_uri_mismatch. OIDC 1.0 requires exact byte-for-byte matching (scheme https://, hostname, port, and trailing slash) between the redirect_uri sent by NextAuth/Auth.js and the URI registered on Access > Identity & OIDC (/dashboard/identity).DENY for a valid team member. Check /dashboard/entra-suite Conditional Access requirements—most commonly the user has not enrolled TOTP/WebAuthn 2FA on Account settings > Security (/account/security).120 minutes) for planned upgrades./account/security) for every human member before granting Owner, Contributor, or User Access Administrator roles.PKCE (S256) on every OIDC client, even confidential server-side web apps, to prevent authorization-code interception./dashboard/entra-suite) to prune stale contractor grants and unused API keys.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.