okta
π―SkillInstallation
npx skills add g1joshi/agent-skills --skill oktaRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/oktaInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/okta/ - All projects
~/.claude/skills/okta/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View on GitHub βExpert Okta identity cloud assistance covering workforce identity, customer identity (CIAM), SAML, and API authorization servers. Use when configuring Okta SSO, managing enterprise directories, or securing APIs.
Okta
Okta is the enterprise standard for Identity and Access Management (IAM). While Auth0 (owned by Okta) targets developers/B2C, "Okta Workforce Identity" targets employee access and large B2B integrations.
When to Use
- Enterprise Workforce Identity: Centralizing employee single sign-on, lifecycle provisioning, and multi-factor authentication.
- Customer Identity and Access Management (CIAM): Deploying scalable customer authentication backed by Okta Customer Identity Cloud.
- B2B SAML / WS-Fed Enterprise Federation: Federating customer Active Directory or Okta instances into your SaaS platform.
- Zero-Trust Network Access & Device Trust: Enforcing device posture checks and context-aware access policies.
Quick Start
npm install @okta/okta-react @okta/okta-auth-js
import { Security, LoginCallback } from "@okta/okta-react";
import { OktaAuth } from "@okta/okta-auth-js";
const oktaAuth = new OktaAuth({
issuer: "https://{yourOktaDomain}/oauth2/default",
clientId: "{clientId}",
redirectUri: window.location.origin + "/login/callback",
});
function App() {
return (
<Security oktaAuth={oktaAuth}>
<Route path="/login/callback" component={LoginCallback} />
<SecureRoute path="/protected" component={MyProtectedPage} />
</Security>
);
}
Core Concepts
Okta Application Models & Sign-On Policies
Applications in Okta represent integration targets with distinct security policies:
[ User Directory (Okta Universal Directory) ]
βββ [ App: AWS IAM Federation (SAML 2.0) ]
βββ [ App: Internal Engineering Portal (OIDC + PKCE) ]
βββ [ App: Salesforce (SAML + SCIM Provisioning) ]
Okta JWT Token Verification via Okta JWT Verifier
Validates tokens issued by Okta Authorization Servers:
import OktaJwtVerifier from "@okta/jwt-verifier";
const oktaJwtVerifier = new OktaJwtVerifier({
issuer: "https://my-company.okta.com/oauth2/default",
clientId: "0oa1234567890abcdef",
assertClaims: {
"groups.includes": "Engineering",
},
});
export async function verifyOktaToken(authHeader: string) {
const token = authHeader.replace("Bearer ", "");
const jwt = await oktaJwtVerifier.verifyAccessToken(token, "api://default");
return jwt.claims;
}
SCIM 2.0 Automated User Provisioning
Synchronizes user creation, updates, and deprovisioning from Okta to downstream apps automatically:
POST /scim/v2/Users HTTP/1.1
Host: api.mysaas.com
Authorization: Bearer <scim_token>
Content-Type: application/scim+json
{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"userName": "alice@company.com",
"name": { "givenName": "Alice", "familyName": "Smith" },
"active": true
}
Common Patterns
Custom Authorization Server Policy and Scope Enforcement
Problem: Multi-tenant APIs require restricting token issuance to specific organizational scopes and claims.
Solution: Validate custom Okta scopes on inbound API requests:
import { OktaJwtVerifier } from "@okta/jwt-verifier";
const oktaJwtVerifier = new OktaJwtVerifier({
issuer: "https://mycompany.okta.com/oauth2/default",
assertClaims: {
aud: "api://default",
cid: process.env.OKTA_CLIENT_ID,
},
});
export async function verifyOktaScope(token: string, requiredScope: string) {
const jwt = await oktaJwtVerifier.verifyAccessToken(token, "api://default");
if (!jwt.claims.scp || !jwt.claims.scp.includes(requiredScope)) {
throw new Error("Insufficient scope privileges");
}
return jwt;
}
Best Practices
Do:
- Use Custom Authorization Servers for Customer APIs: Keep workforce and customer authentication configurations strictly segregated.
- Implement SCIM Deprovisioning: Ensure deactivated employees in Okta are immediately revoked across all downstream SaaS platforms.
- Enforce FIDO2 / WebAuthn Factors: Prioritize phishing-resistant Fast IDentity Online (FIDO2) authenticators over SMS OTP.
- Cache Public Keys (JWKS) Gracefully: Use built-in verifier caching to avoid hitting Okta rate limits on token validation.
Don't:
- Hardcode API tokens with Super Admin permissions: Create granular service accounts with least-privilege administrative roles.
- Allow unencrypted HTTP endpoints in Okta App redirect URIs: Enforce HTTPS on all registered redirect destinations.
- Disable rate limit alerts: Monitor Okta System Log webhooks for security alerts and rate limit warnings.
Troubleshooting
| Error | Cause | Solution |
|---|---|---|
403 Forbidden | User not appointed to App. | Assign the User or Group to the Application in Okta Console. |
Clock Skew | Server time mismatch. | Ensure servers utilize NTP; JWT validation allows ~2 min skew. |
References
More from this repository10
A template skill providing a starter framework for creating new agent skills with structured sections for triggers, quick start examples, and capability descriptions.
Skill
Skill
Skill
Skill
Skill
Skill
Skill
Skill
Skill