Start a fresh conversation. Replace the highlighted placeholders.
Use identity-federation to create a safe, staged test plan for suspected [SAML, OIDC, or OAuth issue] on [target] under [written authorized scope], explicitly accounting for user-lockout risk from token replay tests and requiring my confirmation before active testing.
Required inputs
[SAML, OIDC, or OAuth issue]
[target]
[written authorized scope]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
⚠️ AUTHORIZED USE ONLY
This skill is for educational purposes or authorized security assessments only.
You must have explicit, written permission from the system owner before using this tool.
Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate
Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:
Ask the user to state the exact target URL, IP, account, or resource.
Ask the user to confirm written authorization and the permitted scope.
Show the exact command(s) and explain their expected effect.
Wait for explicit confirmation in the current conversation.
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
Identity Federation (SAML / OIDC / OAuth)
When to Use
Testing SSO/federation flows within an approved scope.
Hunting signature-validation or audience-confusion flaws.