Weave Code
Okta Laravel Package
socialiteproviders/okta
Okta OAuth provider for Laravel Socialite, part of the Socialite Providers collection. Adds Okta single sign-on to Laravel apps via simple driver registration and config, using standard Socialite flows. Lightweight, community-maintained, and easy to drop in.
Okta provider for Laravel Socialite, part of the Socialite Providers collection. It lets you authenticate users against your Okta organization using OAuth 2.0 / OpenID Connect, returning a standard Socialite user object you can drop into an existing login flow.
- Sign in with Okta org credentials via OAuth 2.0 / OpenID Connect
- Configurable Okta domain and authorization server
- Maps Okta profile claims (name, email, locale) to Socialite's user
- Installs via Composer and registers through the Socialite Providers listener
Frequently asked questions about Okta
- How do I install socialiteproviders/okta in a Laravel app?
- Install it with Composer using composer require socialiteproviders/okta. Register the SocialiteWasCalled listener so the okta driver is added to Laravel Socialite at runtime. Add an okta entry to config/services.php with your client ID, client secret, redirect URI, and Okta domain. Then create an Okta OIDC application and set its redirect URI to match your Laravel callback route.
- How do I configure the Okta driver for Laravel Socialite?
- Put your Okta OAuth2/OIDC application credentials in config/services.php under an okta key, typically sourced from environment variables. The driver needs the client ID, client secret, redirect URI, and your Okta organization domain or base URL. The redirect URI in Laravel must exactly match the sign-in redirect URI configured in the Okta application. After configuration, call Socialite::driver('okta') in your controller.
- Which Laravel, PHP, and Socialite versions does socialiteproviders/okta support?
- The package is a Socialite driver, so its Composer constraints must be checked against your PHP, Laravel, and laravel/socialite versions. It also depends on the SocialiteProviders Manager at runtime for driver registration. Because this is a community subtree split, validate compatibility with Composer pins and a CI matrix rather than assuming broad version support. Use composer why-not to catch conflicts before upgrading Laravel or Socialite.
- How do I implement Okta redirect and callback routes with Socialite::driver('okta')?
- Create a redirect route that returns Socialite::driver('okta')->redirect() to send users to Okta. Create a callback route that calls Socialite::driver('okta')->user() to exchange the authorization code and retrieve the user. Keep OAuth state handling and error paths intact, including denied consent and invalid or expired credentials. Map the returned Okta subject to a local user record rather than relying only on email.
- Does socialiteproviders/okta support Okta SAML, SCIM, group sync, or adaptive MFA policies?
- No, this package is a thin OAuth2/OIDC login adapter for Laravel Socialite. It does not replace Okta or provide enterprise identity features such as SAML, SCIM provisioning, group synchronization, advanced token validation, or adaptive MFA policy handling. If you need those capabilities, use Okta's platform features or dedicated SDKs alongside this login driver. Treat it as an authentication adapter, not your full identity architecture.
- Can I map Okta groups or roles to Laravel roles with this provider?
- The package has limited first-class claim mapping, so group and role mapping usually requires custom logic. You can inspect the claims returned by the Okta user object, but you may need to configure Okta to include group claims in the ID token or userinfo response. Keep local authorization decisions in Laravel and use the Okta subject as the stable identity key. Avoid using email alone as the account-linking key.
- Is socialiteproviders/okta maintained and safe to use in production?
- It is a read-only subtree split of the SocialiteProviders monorepo, so GitHub stars and issues undercount actual usage. The last release was in April 2025, which is acceptable but not frequently active, and there is no vendor SLA. Use it conditionally for low-to-medium-criticality Laravel apps with pinned versions, staging validation, and a fallback plan. For high-assurance enterprise SSO, require a security review and confirm upstream maintenance before adopting it.
- What are the alternatives to socialiteproviders/okta for Laravel?
- Alternatives include building a custom Laravel Socialite driver around Okta's OIDC endpoints, using Okta's official SDKs directly, or adopting a commercially supported SSO integration. If you need SAML, SCIM, or advanced Okta policy handling, a Socialite login driver alone will not cover it. Teams already standardized on Socialite often choose this package because it avoids custom OAuth plumbing. Evaluate alternatives against your need for support, token validation, and long-term maintenance.
- How should I test Okta login in a Laravel application?
- Use a separate Okta application and redirect URI for each environment, including local development and staging. Test successful login, denied consent, expired client secret, missing claims, logout, and account-linking behavior before production. In automated tests, mock the Socialite driver or HTTP responses rather than calling the real Okta tenant. Complete a security review of OAuth state, PKCE expectations, and token handling as part of the rollout.
- What should I check before using this package for enterprise SSO?
- Confirm which Okta flows you need: OIDC web login only, or SAML, SCIM, single logout, MFA claims, and adaptive policies. Verify that the package constraints match your PHP, Laravel, and Socialite versions and that listener registration works with your Laravel version. Clarify ownership of Okta app registration, redirect URIs, secret rotation, and environment promotion. Finally, review audit, data residency, account linking, and the fallback plan if the community package lags upstream releases.
Weaver
How can I help you explore Laravel packages today?