What problem does it solve?
Setting up Okta SSO in a Webiny project requires coordinating API-side JWT claim mapping, React extension registration, environment variables, and deployment across both API and Admin apps. This Skill guides that entire integration so developers can replace the default Cognito authentication with Okta without missing any wiring steps.
Core Features & Use Cases
- Identity Mapping: Implements
OktaIdpConfig.Interface to map Okta JWT claims (sub, name, roles, teams, profile) to Webiny identity data, with optional custom claim verification.
- Extension Setup: Creates a React extension component using
<Okta /> from @webiny/okta that injects environment variables, registers OIDC token verification, and configures the Admin login screen.
- DI Integration: Supports injecting Webiny services like
TenantContext into the config class via the dependency injection pattern for tenant-aware identity resolution.
- Use Case: A team wants employees to log into the Webiny Admin app through their corporate Okta directory. The Skill produces the config class, extension component, registration in
webiny.config.tsx, and the OKTA_ISSUER/OKTA_CLIENT_ID environment setup, followed by deployment.
Quick Start
Ask the AI to configure Okta as the identity provider for your Webiny project and replace the default Cognito authentication.
