Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog

Loading…

Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Docs
  • Documentation Hub
  • Choose a Product
    VMs, Containers & Cloud
  • First Linux Server
    SSH, Firewall & Apps
  • Windows Server 2025
    BYOL & Remote Desktop
  • Remote Access
  • Troubleshooting
  • FAQ
  • All Product Guides
    29 Step-by-Step Guides
  • Cloud & SaaS Catalog
    112 Cloud & SaaS Offerings
  • Azure Cloud Storage
    Hot/Cool/Archive & WORM
  • Resource Manager & RBAC
    Groups, Tags & Locks
  • Multi-Model Cloud DB
    JSONB, SQL & pgvector
  • Cloud Identity & ZTNA
    OIDC, SCIM & PIM
  • Key Vault & KMS
    Secrets & Envelope Keys
  • Cloud SIEM, SOAR & DLP
    Posture & Threat Response
  • API Gateway & Cloud DNS
    Edge WAF & DNS Zones
  • Serverless, Workflows & IoT
    Functions, Queues & DAGs
  • SaaS, Governance & Vault
    Budgets & Off-Host GRS
  • Build Web Apps with AI
  • Next.js and React
  • TypeScript and Node.js
  • npm and Tooling
  • Data and APIs
  • Deploy and Operate
  • Tutorials
  • Infrastructure
  • Automation & Regions
  • API Overview
  • API v1 Reference
    Endpoints & 23 Scopes
  • MCP Server
    129 AI Agent Tools
  • Swagger / OpenAPI 3.1
  • API Playground
  • Versioning & Sunset
  • API Token Security
    Authentication & Tokens
  • Instances API
    Compute Resources
  • Networking API
    Networks & Ports
  • Storage API Availability
    Volumes & Backups
  • Webhooks & Events
    Event Notifications
  • Rate Limits & Best Practices
    Throttling & Retries
  • sau CLI Reference
    34 Commands (v0.2)
  • Browser Web CLI
  • SDKs
  • Infrastructure as Code
    Terraform & Ansible
  • Code Examples
  • CLI & SDK Guides
  • Security Guides
  • Security at a Glance
  • Zero Trust Architecture
  • Live Trust Center
  • Compliance
Need help?

Loading documentation...

Documentation/products

Configure OIDC 1.0, SCIM 2.0, ZTNA and Cloud Bastion

Set up multi-tenant OIDC SSO, ES256 JWKS, SCIM provisioning, W3C Verified Credentials, ZTNA access and zero-public-IP Cloud Bastion.

Advanced
25 min
Updated 2026-11-12

Deploy Ready-to-Run Infrastructure in Seconds

Linux VMs from $6/mo · Pooled Virtual Datacenters from $12/mo · Use code WELCOME20 for 20% off your first order.

Browse ServersView Pricing

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.

What you will have at the end

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

Before you start

  • A Servers Are Up account signed in at /dashboard.
  • A Personal Access Token with cloud:read and cloud:write scopes (Account settings > API keys at /account/api-keys).
  • At least one internal web application (such as GitLab, Grafana, LibreChat, or your own Next.js app) or private VM that you want to protect behind SSO, ZTNA, and Cloud Bastion.

Steps

1. Register an OIDC 1.0 SSO application and inspect ES256 JWKS

Open Access > Identity & OIDC (/dashboard/identity):

  1. Inspect your tenant's OpenID Connect discovery metadata and public ES256 JSON Web Key Set (JWKS) URL (/.well-known/openid-configuration via /api/v1/identity).
  2. Click Register OIDC Client / Enterprise App, enter your application's display name (for example Internal Engineering Portal), and register its exact HTTPS callback URI (https://portal.example.com/api/auth/callback/sau).
  3. Enable PKCE (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.

2. Enforce ZTNA Private Access policies and Conditional Access

Open Access > Identity governance & ZTNA (/dashboard/entra-suite) to govern who can reach which internal hostname under what device, MFA, and IP risk posture:

  1. Create a Zero-Trust Private Access (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.
  2. Schedule recurring Access Reviews and inspect CIEM (Cloud Infrastructure Entitlement Management) findings to strip unused over-privileged permissions.
  3. Test policy evaluation directly from the 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"

3. Issue W3C Verifiable Credentials (ES256) for high-assurance operators

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

4. Replace public SSH/RDP ports with Cloud Bastion JIT jump sessions

Instead of opening TCP 22 or 3389 on any virtual machine's public IP:

  1. Keep inbound 22 and 3389 closed on Network > Firewall (/dashboard/network?tab=firewall).
  2. Open Access > Cloud bastion (/dashboard/bastion) (or run sau network bastion-list -o table).
  3. Request an ephemeral Just-In-Time (JIT) SSH or WebRDP session ticket (for example 60 minutes, tied to a ticket reason such as INC-402 database index tune).
  4. Launch the browser SSH or WebRDP workspace directly through the Bastion tunnel—every session start, command stream metadata, and termination is recorded in your immutable audit log.
# Audit active Cloud Bastion hosts and ephemeral JIT tickets
sau network bastion-list -o table

Check that it works

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.

What can go wrong

  • OIDC login fails with 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).
  • ZTNA evaluation returns 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).
  • Bastion JIT ticket expires mid-maintenance. JIT tickets intentionally expire at their TTL boundary; request a fresh ticket or configure a longer maintenance window (120 minutes) for planned upgrades.

Good practice

  • Require Phishing-Resistant MFA (Passkeys / WebAuthn) or TOTP 2FA on Account settings > Security (/account/security) for every human member before granting Owner, Contributor, or User Access Administrator roles.
  • Enforce PKCE (S256) on every OIDC client, even confidential server-side web apps, to prevent authorization-code interception.
  • Run monthly Access Reviews in Access > Identity governance & ZTNA (/dashboard/entra-suite) to prune stale contractor grants and unused API keys.

Where to go next

  • Store AES-256-GCM secrets and rotate keys in Key Vault
  • Organize resources with groups, tags, locks and RBAC
  • Hunt threats with KQL, automate SOAR and enforce DLP

Related Articles

Create a scoped API key and send your first v1 request

Read more

Route APIs with Edge WAF, rate limits and Cloud DNS

Read more

Purchase Azure-backed cloud storage with WORM locks and SAS

Read more

Frequently Asked Questions

What does the Configure OIDC 1.0, SCIM 2.0, ZTNA and Cloud Bastion documentation guide cover?
Set up multi-tenant OIDC SSO, ES256 JWKS, SCIM provisioning, W3C Verified Credentials, ZTNA access and zero-public-IP Cloud Bastion. It is rated advanced difficulty (25 min) and applies to Servers Are Up infrastructure and workflows.
Can I manage or automate these steps through the Servers Are Up dashboard, REST API v1, or MCP server?
Yes. Every Servers Are Up server includes browser-based SSH, WebRDP, and VNC console access in the dashboard, plus programmatic control via the REST API v1 (/api/v1) and hosted Model Context Protocol server (/api/mcp/v1) using a scoped Personal Access Token.

Need hands-on help with Configure OIDC 1.0, SCIM 2.0, ZTNA and Cloud Bastion?

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.

Was this article helpful?

On this page

What you will have at the endBefore you startSteps1. Register an OIDC 1.0 SSO application and inspect ES256 JWKS2. Enforce ZTNA Private Access policies and Conditional Access3. Issue W3C Verifiable Credentials (ES256) for high-assurance operators4. Replace public SSH/RDP ports with Cloud Bastion JIT jump sessionsCheck that it worksWhat can go wrongGood practiceWhere to go next