Jboss Keycloak SAML Single sign-on (SSO) is an authentication method that enables Jboss Keycloak users to access multiple Joomla applications with one login and one set of credentials.
What is SSO ?
Single sign-on (SSO) is anauthenticationmethod that enables users to access multiple applications with one-click login and one set of credentials. For example, after users log in to your org, they can automatically access all apps from the App Launcher. When you set up SSO, you configure one system to trust another to authenticate users , eliminating users' need to log in to each system separately. The system that authenticates users is called an Identity provider. The system that trusts the identity provider for authentication is called the Service provider.
SAML allows exchanging of information betweenService ProviderandIdentity provider, SAML isintegration between SP and IDP. When a user tries to log in, your identity provider sends SAML assertions containing facts about the user to Identity Provider. Identity Provider receives the assertion, validates it against your Identity Provider configuration, and allows the user to access your org.
Our plugin is compatible with Joomla 4 as well as with all the SAML 2.0 compliant Identity Providers. Here we will go through a step-by-step guide to configure SAML SSO login between Joomla site and Jboss Keycloak by considering Jboss Keycloak as IdP (Identity Provider & Joomla as SP (Service Provider).
If you want support in configuring the plugin, or to integrate Jboss Keycloak with Joomla, click on Free Configuration Setup button.
We provide a 7 day full feature trial wherein you can fully test out all the features of the plugin, click on Free Business Trial button.
| Client ID | SP-EntityID/Issuer from Service Provider Metadata |
| Client protocol | SAML |
| Client SAML Endpoint (optional) | The ACS (Assertion Consumer Service) URL from Service Provider Metadata |
| Client ID | The SP-EntityID / Issuer from Service Provider Metadata |
| Name | Provide a name for this client (Eg. Joomla) |
| Description (optional) | Provide a description |
| Enabled | ON |
| Consent Required | OFF |
| Client Protocol | SAML |
| Include AuthnStatement | NO |
| Sign Documents | NO |
| Optimize Redirect signing key lookup | OFF |
| Sign Assertions | NO |
| Signature Algorithm | RSA_SHA256 |
| Encrypt Assertion | OFF |
| Client Signature Required | OFF |
| Client Signature Required | EXCLUSIVE |
| Force Name ID Format | NO |
| Name ID Format | |
| Root URL | Leave empty or Base URL of Service Provider |
| Valid Redirect URIs | The ACS (Assertion Consumer Service) URL from Service Provider Metadata |
| Assertion Consumer Service POST Binding URL | The ACS (Assertion Consumer Service) URL from Service Provider Metadata |
| Logout Service Redirect Binding URL | The Single Logout URL from Service Provider Metadata |
Add Mappers
Add User
OR
| Identity Provider Name | Provide an Identity Provider name (For Example: Keycloak). |
| IdP Entity ID or Issuer | Search for the entityID from IDP Metadata.Enter the Value in the Entity ID textbox. |
| SAML Login URL | Search for SingleSignOnService Binding ”urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect” from IDP Metadata.Enter the location value in the SAML Login URL textbox. |
| SAML Logout URL (Optional) | Search for SingleLogoutService Binding”urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect” from IDP Metadata.Enter the location value in the SAML Login URL textbox. |
| X.509 Certificate (Optional) | Search for the X.509 Certificate from IDP Metadata.Enter the tag value in Certificate textbox. |
| Enable login with SAML | Checked |
| Signed SSO and SLO Requests | Unchecked |
By Metadata URL :
By Uploading Metadata File: 
Manual Configuration : | IdP Entity ID or Issuer | SAML Entity ID in the Federation Metadata document |
| Single Sign-On Service URL | SAML Single-Sign-On Endpoint URL in the Federation Metadata document |
| X.509 Certificate | x.509 Certificate in the Federation Metadata document |
Add a button on your site login page with the following URL:
By Metadata URL :
By Uploading Metadata File: 
Manual Configuration : | IdP Entity ID or Issuer | SAML Entity ID in the Federation Metadata document |
| Single Sign-On Service URL | SAML Single-Sign-On Endpoint URL in the Federation Metadata document |
| X.509 Certificate | x.509 Certificate in the Federation Metadata document |
Add a button on your site login page with the following URL:
| Username: | Name of the username attribute from IdP (Keep NameID by default) |
| Email: | Name of the email attribute from IdP (Keep NameID by default) |
| Group/Role: | Name of the Role attribute from Identity Provider(IdP) |
You have successfully completed your miniOrange SAML 2.0 SP configurations. Still, if you are facing any difficulty please mail us on joomlasupport@xecurify.com .
Synchronize users, groups & directory with SCIM & REST APIs for Server.
Page Restriction plugin restricts Joomla pages (Articles) based on User Roles and User's Login Status.
Using this Add-on you would be mapping the user details into the CB's comprofilers fields table which contains the values.
If you want Business Trial for FREE Click Here
If you don't find what you are looking for, please contact us at joomlasupport@xecurify.com or call us at +1 978 658 9387.
Need Help? We are right here!
