SEG FCU Transformation

Cognizant Direct Browser PKCE SSO

Signing in via Interactive Browser OAuth 2.0 + PKCE (/oauth2/v2.0/authorize) directly from your compliant Windows 10 device:

PKCE-S256

✓ Why Direct Browser PKCE Fixes Error 530033 & 53003 Compliant Device

Why "Sign in another way" is not needed: Your account (Connected to Windows) uses your Windows 10 Primary Refresh Token (Device state: Compliant) automatically when you click your account tile.
Why Error 530033 happened on /device: Device Code Flow treats Cloudflare (172.69.x.x) as "another device" (unmanaged). Direct Browser PKCE (/oauth2/v2.0/authorize) makes your compliant Windows 10 laptop the requesting device.

After clicking your Cognizant account in the right popup, it redirects to http://localhost:8400/?code=... (no local server is needed — copy that URL from the popup's top address bar and click "Complete Sign-In from Clipboard" or paste it below):

Waiting for you to select your Cognizant account in the popup... PKCE Ready

Zero-Config (04b07795...7b46)

Callback: ... PKCE S256

or use Cognizant ID credentials

New here? Configure Azure App Registration

INTERNAL • SEG FRONTIER CAPABILITY UNITS

Unauthenticated

Select Authentication Mode (No Env Vars Required)

Active OIDC Parameters

Saved dynamically to Cloudflare Edge / Python Backend + Browser Storage

Cognizant Tenant ID (CTS_TENANT_ID)

Application (Client) ID (CTS_CLIENT_ID)

Client Secret (CTS_CLIENT_SECRET) — Optional for Public/SPA; Used by Edge/Python Confidential Client

Redirect URI (REDIRECT_URI)

Quick Presets:

OIDC Scopes (SCOPES)