WordPress Single Sign-On (SSO) Plugin module allows users to login into a WordPress site using their Okta credentials. This enables seamless login between WordPress and Okta thereby eliminating the need to remember passwords for each application. The Single Sign-On (SSO) functionality is achieved using OAuth / OpenID Connect protocol. WordPress acts as an OAuth Client and Okta as an OAuth Provider.
The Single Sign-On Solution
Before OAuth, HTTP was the Basic Authentication standard, where the user is prompted for a username and password for accessing each application. Websites would prompt you to enter your username and password directly into a form and they would log in to your data (e.g. your Gmail account) as you.
Basic Authentication is still used as a primitive form of API authentication for server-side applications wherein instead of sending a username and password to the server with each request, the user sends an API key ID and secret.
Contrary to the above, OAuth allows authentication using access tokens which is more secure as no sharing of passwords is involved.
- Unlimited SSO Authentications: Users can log in to WordPress using SSO any number of times.
- Auto-create users / Just In Time user provisioning: During SSO login, if the Okta user doesn’t exist in WordPress, then the user account will be created automatically.
- Account linking: During SSO login, if the Okta user already exists in WordPress, then the user account will be linked to the same existing account and the user profile will be updated.
- Attribute mapping: Map the user attributes that you get from Okta to the user profile in WordPress.
- SSO login widget: Integrate SSO in the WordPress site by placing the SSO login widget wherever you want.
- Redirect after SSO login: After successful SSO login, users will be redirected to the homepage of your WordPress site.
- Grant type support: Supports the standard OAuth2 grant which is the most secure of all the grant types: Authorization Code grant.
- Debug logging: If you run into any issues with the SSO login, debug logs would be helpful.
If you have any questions regarding the WordPress Okta SSO please contact us at [email protected].
Add this integration to enable authentication and provisioning capabilities.
- Event Hooks
- Inbound Federation
- Inline Hooks
- Outbound Federation
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- Workflow Templates
- Workflows Connectors
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Attribute Sourcing The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.
Here is a section all about documentation, integration, and implementation.