Detecting Auth... 0 Groups 0 Roles

Authenticating...

-

Principal ID / OID Not detected
Entra ID App Roles
No groups detected
Privilege Status
Checking groups...

🔀 Dynamic Reverse Proxy Routing

Nginx uses regex ^/api/(<backend>)/(.*) to forward directly to internal containers.

ℹī¸
Direct Container Proxy Active: Nginx extracts the second path parameter and proxies directly to http://<backend>/.... No intermediate gateway container. Auth headers and cookies are forwarded directly.
ACTIVE DISPATCH TARGET: GET /api/backend1/add?a=15&b=35

Backend Microservices & Method Explorer

Select a backend container and choose any method to execute.

1. SELECT BACKEND CONTAINER:
Backend 1 🛡ī¸ User App Role

Core Calculation Service. Mandatory User App Role policy for GET and POST.

GET & POST: User | Caller Guard: /backend3/health
Backend 2 🔍 Auditor / ❌ Misconfigured

Auditor & Misconfigured Demo: GET requires Auditor, POST is unconfigured.

GET: Auditor | POST: Misconfigured (403)
Backend 3 🔒 Multi-Role GET / Admin POST

High-privilege Service: GET allows User, Auditor, Admin; POST requires Admin.

GET: User, Auditor, Admin | POST: SecurityAdmin
Identity Service 🔑 Auth & Graph

Dedicated Service: /.auth/me emulation, WhoAmI introspection & Microsoft Graph API.

Endpoints: /.auth/me, /whoami, /graph/*
2. SELECT ENDPOINT / METHOD FOR BACKEND 1:
+

Response & Zero-Trust Insight

Ready to execute

Ready - ms
💡
Select any backend and method, then click Execute Call to test zero-trust App Role enforcement. 
// Response will appear here