Search Results :
×Set up Single Sign-On (SSO) on your WordPress website via Keycloak WordPress SSO with the WP OAuth & OpenID Connect Single Sign-On plugin. Implementing WordPress SSO using Keycloak allows users to log into your websites and applications with a single set of credentials using the Keycloak SSO OAuth provider.
Keycloak, acts as the OAuth Provider, and WordPress act as the OAuth Client. WordPress Keycloak SSO provides smooth login between WordPress and Keycloak using login with Keycloak SSO with a single click. The WordPress SSO plugin also provides advanced Keycloak SSO features like user profile attribute mapping, role mapping, and providing site access based on organization email domains. You can also protect your complete WordPress site behind SSO. Keycloak WordPress OAuth SSO plugin secures the user’s login process and improves user authentication using Keycloak WordPress SSO. Follow the steps in the guide below to Setup Your WordPress SSO via installing this plugin.
For the Keycloak Version 16 and below |
Go to the Root Directory of keycloak bin standalone.sh |
For the Keycloak Version 17 and above |
Go to the Root Directory of keycloak bin kc.bat and run the below commands.
|
Follow the following steps to configure Keycloak as IdP to achieve WordPress Keycloak SSO
NOTE : Disabling Temporary will make user password permanent.
Step 1.1: Steps to fetch Keycloak Groups [Premium]
Note: -- If full path is on group path will be fetched else group name will be fetched.
Step 1.2: Steps to fetch Keycloak Roles [Premium]
NOTE : Disabling Temporary will make user password permanent.
NOTE : Disabling Temporary will make user password permanent.
Note: -- The domain name would be the domain of the machine where your keycloak is running followed by the port number, for e.g if your keycloak is running on localhost then the domain would be http://localhost:8080.
In conclusion , You have successfully configured WordPress as OAuth Client, for achieving Keycloak Single Sign-On (SSO) with WordPress for user authentication.
Note: -- The domain name would be the domain of the machine where your keycloak is running followed by the port number, for e.g if your keycloak is running on localhost then the domain would be http://localhost:8080.
In conclusion , You have successfully configured WordPress as OAuth Client, for achieving Keycloak Single Sign-On (SSO) with WordPress for user authentication.
Sign in settings for WordPress 5.7 and before
Sign in settings for WordPress 5.8
Sign in settings for WordPress 5.9
Please refer the below table for configuring the scope & endpoints for Keycloak Version 18 and above in the plugin.
Scope: | email profile openid |
Authorize Endpoint: | <keycloak domain>/realms/{realm-name}/protocol/openid-connect/auth |
Access Token Endpoint: | <keycloak domain>/realms/{realm-name}/protocol/openid-connect/token |
Get User Info Endpoint: | <keycloak domain>/realms/{realm-name}/protocol/openid-connect/userinfo | Custom redirect URL after logout: [optional] | https://{keycloak domain}/realms/{realm-name}/protocol/openid-connect/logout?post_logout_redirect_uri={encodedRedirectUri}&id_token_hint=##id_token## |
Please refer the below table for configuring the scope & endpoints for Keycloak Version 17 and below in the plugin.
Scope: | email profile openid |
Authorize Endpoint: | <keycloak domain>/auth/realms/{realm-name}/protocol/openid-connect/auth |
Access Token Endpoint: | <keycloak domain>/auth/realms/{realm-name}/protocol/openid-connect/token |
Get User Info Endpoint: | <keycloak domain>/auth/realms/{realm-name}/protocol/openid-connect/userinfo | Custom redirect URL after logout: [optional] | <keycloak domain>/auth/realms/{realm-name}/protocol/openid-connect/logout?redirect_uri=encodedRedirectUri |
You have successfully enabled WordPress SSO Login with the WordPress OAuth & OpenID Connect Single Sign-On (SSO) plugin by configuring Keycloak as IdP (OAuth Provider) and WordPress as an OAuth client. Keycloak OAuth Authorization means you can quickly roll out secure access to your WordPress(WP) site, allowing users to safely authenticate using Keycloak SSO login credentials.
Login to the Keycloak administration console. Go to the Realm settings -> general section, and you will get the Realm name. Read more
Get prompt support from our technical experts, accessible around the clock for direct assistance
Get access to our detailed knowledge base, which includes comprehensive guides and instructional videos.
We offer Secure Identity Solutions for Single Sign-On, Two Factor Authentication, Adaptive MFA, Provisioning, and much more.
Please contact us at +1 978 658 9387 (US) | +91 97178 45846 (India) oauthsupport@xecurify.com
Need Help? We are right here!
Thanks for your inquiry.
If you dont hear from us within 24 hours, please feel free to send a follow up email to info@xecurify.com
This privacy statement applies to miniorange websites describing how we handle the personal information. When you visit any website, it may store or retrieve the information on your browser, mostly in the form of the cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not directly identify you, but it can give you a more personalized web experience. Click on the category headings to check how we handle the cookies. For the privacy statement of our solutions you can refer to the privacy policy.
Necessary cookies help make a website fully usable by enabling the basic functions like site navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any personal identifiable information. However, some parts of the website will not work properly without the cookies.
These cookies only collect aggregated information about the traffic of the website including - visitors, sources, page clicks and views, etc. This allows us to know more about our most and least popular pages along with users' interaction on the actionable elements and hence letting us improve the performance of our website as well as our services.