okta-attack

Map Okta-as-IdP attack surfaces for tenant discovery, user enumeration, and MFA analysis.

Updated May 31, 2026
One-click install
npx skills add https://github.com/grivera82/pi-bughunter --skill okta-attack-grivera82
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okta-attack
Source: https://github.com/grivera82/pi-bughunter/tree/main/skills/okta-attack
Command: npx skills add https://github.com/grivera82/pi-bughunter --skill okta-attack-grivera82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured playbook to assess Okta as an identity provider in red-team engagements, detailing tenant discovery, user enumeration vectors, MFA configuration awareness, and post-compromise exposure surfaces across federated apps and IdP integrations.

Core Features & Use Cases

  • Tenant discovery across Okta domains and federation endpoints (e.g., tenant.okta.com, tenant.okta-emea.com, oktapreview.com).
  • User enumeration and authentication-flow analysis using primary Okta endpoints such as /api/v1/authn, /oauth2, and per-app SAML configurations.
  • Password spray discipline and MFA configuration assessment with risk-aware guidance and rate-limiting considerations.
  • Per-app misconfiguration checks (redirect_uris, SAML attributes, app metadata) and post-compromise API surface exploration.
  • Evidence collection, reporting templates, and remediation guidance for red-team findings.

Quick Start

Map the target Okta tenant domains and known IdP configurations to scope the engagement and begin the discovery workflow.

Frequently Asked Questions about okta-attack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform Okta tenant discovery for a red-team engagement?

Okta tenant discovery involves mapping target domains like tenant.okta.com, tenant.okta-emea.com, and oktapreview.com to identify federation endpoints and scope the engagement. This playbook provides a structured workflow to systematically document these surfaces and their configurations.

What is the best way to enumerate users and analyze Okta authentication flows?

User enumeration and authentication-flow analysis in Okta target primary endpoints such as /api/v1/authn, /oauth2, and per-app SAML configurations. This playbook guides mapping these vectors to identify valid users and assess authentication mechanisms safely.

How do I assess MFA configurations and prevent push-fatigue during Okta password spraying?

Assessing MFA configurations requires risk-aware password spray discipline and rate-limiting considerations to avoid triggering push-fatigue or account lockouts. The playbook outlines how to evaluate MFA setups and apply disciplined spraying techniques.

Can I check for Okta per-app misconfigurations like OIDC redirect_uri tampering?

Yes, you can check for per-app misconfigurations by examining OIDC redirect_uris, SAML attributes, and app metadata. This playbook details how to identify these configuration flaws and explore the post-compromise API surface for federated apps.

How do I document Okta red-team findings and provide remediation guidance?

Documenting Okta red-team findings requires gathering artifacts and using reporting templates to structure the evidence. This playbook provides collection methods and remediation guidance to deliver comprehensive reports for identified tenant discovery and authentication vulnerabilities.