Download the PHP package socialiteproviders/okta without Composer
On this page you can find all versions of the php package socialiteproviders/okta. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package okta
Okta
Installation & Basic Usage
Please see the Base Installation Guide, then follow the provider specific instructions below.
Add configuration to config/services.php
Multi Tenant SSO
If you need to authenticate users from multiple okta instances, you can dynamically set the configuration values prior to calling the redirect
/user
methods. You'll still need to add the services entry as per above, but you can leave all the values as null
.
Custom Auth Server
If you're using Okta Developer you should set auth_server_id
config option appropriately. It should be set to "default", or to the server id of your Custom Authorization Server.
For more information, see the okta docs.
Add provider event listener
Laravel 11+
In Laravel 11, the default EventServiceProvider
provider was removed. Instead, add the listener using the listen
method on the Event
facade, in your AppServiceProvider
boot
method.
- Note: You do not need to add anything for the built-in socialite providers unless you override them with your own providers.
Laravel 10 or below
Configure the package's listener to listen for `SocialiteWasCalled` events. Add the event to your `listen[]` array in `app/Providers/EventServiceProvider`. See the [Base Installation Guide](https://socialiteproviders.com/usage/) for detailed instructions.Usage
You should now be able to use the provider like you would regularly use Socialite (assuming you have the facade installed):
Store a local copy in your callback:
Generate the logout url from your controller:
Refresh Token
Using a refresh token allows an active user to maintain their session:
NOTE: obtaining a refresh_token
requires the scope offline_access
on the initial login.
See additional documentation here.
Client Token
To obtain a client access token for authenticating to other apps without a user:
NOTE: no caching of this token is performed. It's strongly suggested caching the token locally for its ttl
Revoke Token
Mark a token as revoked when checked against an introspection endpoint
Returned User fields
id
email
email_verified
nickname
name
first_name
last_name
profileUrl
address
phone