Jwt 403 Debug Expert
Diagnose 401/403 responses at the AI Citadel APIM gateway — decode JWT claims, verify Access Contract scope grants, and validate Foundry managed-identity token audience.
Install
$ agentstack add skill-aiappsgbb-awesome-gbb-jwt-403-debug-expert ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-aiappsgbb-awesome-gbb-jwt-403-debug-expert) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
jwt403debug_expert
When to use
The SRE Agent should invoke this skill when:
- A user reports a 401 or 403 from the Citadel gateway
- A hosted agent's BYOK call returns "Authentication failed with provider … (HTTP 401)" but the underlying provider is the Citadel-routed AOAI
- After running
citadel-spoke-onboarding, the new spoke can't reach the gateway
Investigation flow
- Get the correlation ID of the failing request from the user or from
the application's logs.
- Pull the request from APIM diagnostics:
``kql ApiManagementGatewayLogs | where TimeGenerated > ago(2h) | where CorrelationId == "" | project TimeGenerated, OperationId, ApiId, ProductId, ResponseCode, BackendStatusReason, LastErrorReason, RequestHeaders, ResponseHeaders ``
- Decode the JWT if present (claims only — NEVER the signature):
aud— must match the gateway URL configured in the Access Contractiss— must behttps://login.microsoftonline.com//v2.0oid— the calling principal's object IDscp/roles— must include the operation scope (e.g.llm:read)exp— must not be in the past
- Match against the Access Contract:
| Symptom | Root cause | Fix | |---|---|---| | aud mismatch | Token issued for wrong audience | Re-issue token with correct audience | | Missing scope claim | Access Contract didn't grant this scope | Re-run citadel-spoke-onboarding with the needed scope in gbb_access_contracts | | exp in past | Token expired (default ~1h for MI) | Refresh; check caller's token-cache TTL | | No Authorization header | Caller using product-key path but no key | Set Ocp-Apim-Subscription-Key or switch to JWT | | 403 with valid JWT | Per-product policy denies | Check rate-limit-by-key and product subscription state |
- Output: classification, root cause hypothesis, ONE recommended fix
and ONE verification step.
Tools
This skill uses:
RunAzCliReadCommandsQueryLogAnalyticsByWorkspaceId
Safety
- NEVER display the JWT signature, named-value contents, or any signing material
- Refer to credentials by resource name only (e.g. "Foundry MI on project
aifp-pilot") - Read-only investigation; any RBAC change requires human action
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aiappsgbb
- Source: aiappsgbb/awesome-gbb
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.