CtrlK
BlogDocsLog inGet started
Tessl Logo

web-auth-mapping

Authentication surface — login endpoints, JWT/OAuth/SAML/SSO/API-key mechanism identification.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/recon/web-recon/auth-mapping/SKILL.md
SKILL.md
Quality
Evals
Security

Authentication Surface Mapping

Map every authentication mechanism the target exposes. Exploit downstream needs to know exactly how to hold a session (cookie, JWT, API key) and where to attack auth (token theft, race-condition on bcrypt, SSO redirect chain).

1. Login Endpoint Discovery

# Common auth paths
for path in login signin auth authenticate oauth/authorize \
    api/auth api/login admin/login wp-login.php; do
    code=$(curl -s -o /dev/null -w "%{http_code}" "https://<target>/$path")
    [ "$code" != "404" ] && echo "$code https://<target>/$path"
done

2. Auth Mechanism Identification

MechanismSignal
Cookie-basedSet-Cookie headers after login (often session=, JSESSIONID=, PHPSESSID=)
JWTAuthorization: Bearer eyJ... patterns; three base64 segments separated by .
OAuth 2.0/oauth/authorize, /oauth/token endpoints; state/code/redirect_uri params
API KeyX-API-Key header accepted; Authorization: ApiKey <token>
SAML/SSORedirects to IdP (Okta, Azure AD, Auth0); SAMLRequest form param
Session row + slow KDFLogin latency >50ms on wrong password (bcrypt/Argon2) — flag for race-condition recon

3. Output for Handoff

Record per mechanism: endpoint, success/fail signals (status code, cookie set, JSON shape), credentials used, observed latency. This feeds the Required session state line in the recon → exploit handoff.

Repository
PurpleAILAB/Decepticon
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.