Search Results :

×
Sign Up Contact Us
The miniOrange team will be in town for WordCamp Europe 2025 - we'd love to meet while we're there! Book a Meeting

Contents

SAML Single Sign-On into Joomla using Azure AD B2C

miniOrange Joomla SAML SP SSO plugin helps you to integrate your Joomla site to Azure AD B2C using SAML 2.0 protocol. The miniOrange Joomla SAML SP Single Sign-on (SSO) plugin is simple to set up Azure AD B2C SSO into Joomla and enable secure login into Joomla. As a result, users can access multiple Joomla applications with one login after authenticating with their Azure AD B2C IDP credentials.

Our plugin is compatible with Joomla 3 as well as Joomla 4 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 the Joomla site and Azure AD B2C by considering Azure AD B2C as IDP (Identity Provider) & Joomla as SP (Service Provider).

download plugin button Download Plugin plugin pricing button plugin pricing button Pricing Plans free trial plugin free trial plugin Free Trial

In this setup, Azure AD B2C serves as the repository for storing users i.e. it will act as the IDP while Joomla is where users will log in using their credentials from Azure AD B2C where Joomla SAML SP SSO Plugin will be installed.

  • Login into your Joomla site’s Administrator console.
  • From left toggle menu, click on System, then under Install section click on Extensions.
  • Now click on Or Browse for file button to locate and install the plugin file downloaded earlier.
Install Joomla SAML SP Plugin
  • Installation of plugin is successful. Now click on Get Started!
Get Started with SAML SP Setup
  • Go to the Service Provider Metadata tab, here you can find the Metadata URL, download the metadata XML file, or you can copy the Entity ID and ACS URL directly.
Get Started with SAML SP Setup
  • Login to your Azure AD B2C administrator dashboard.
  • From the Azure AD B2C tenant, select App registrations, and then select New registration.
Azure AD B2C Dashboard

  • For Name, enter IdentityExperienceFramework.
  • Under Supported account types, select Accounts in this organizational directory only.
Create New Azure AD B2C App

  • Under Redirect URI, select Web, and then enter https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com, where your-tenant-name is your Azure AD B2C tenant domain name.

NOTE: In the following step if the 'Permissions' section is not visible then it might be the reason that you don't have an active AzureAD B2C subscription for that tenant. You can find the details regarding the AzureAD B2C subscription and you can create a new tenant by following the steps here.


  • Under Permissions, select the Grant admin consent to openid and offline_access permissions check box.
  • Select Register.
Create SAML 2.0 Azure AD B2C App

  • Record the Application (client) ID for use in a later step.
Configure Azure AD B2C App

Register the Identity Experience Framework application:

  • Under Manage, select Expose an API.
  • Select Add a scope, then select Save and continue to accept the default application ID URI.
Configure Azure AD B2C Metadata

  • Enter the following values to create a scope that allows custom policy execution in your Azure AD B2C tenant:
    • Scope name: user_impersonation
    • Admin consent display name: Access IdentityExperienceFramework
    • Admin consent description: Allow the application to access IdentityExperienceFramework on behalf of the signed-in user.
  • Select Add scope.
Configure Azure AD B2C Attribute Mapping

Register the ProxyIdentityExperienceFramework application:

  • Select App registrations, and then select New registration.
  • For Name, enter ProxyIdentityExperienceFramework.
  • Under Supported account types, select Accounts in this organizational directory only.
Configure Azure AD B2C Assign People

  • Under Redirect URI, use the drop-down to select Public client/native (mobile & desktop).
  • For Redirect URI, enter myapp://auth.
  • Under Permissions, select the Grant admin consent to openid and offline_access permissions check box.
  • Select Register.
Configure Azure AD B2C Assign Groups

  • Record the Application (client) ID for use in a later step.
Configure Azure AD B2C Assign Groups

Next, specify that the application should be treated as a public client:

  • Under Manage, select Authentication.
  • Under Advanced settings, enable Allow public client flows (select Yes).
  • Select Save.
Configure Azure AD B2C Sign Certificate

Now, grant permissions to the API scope you exposed earlier in the IdentityExperienceFramework registration:

  • Under Manage, select API permissions.
  • Under Configured permissions, select Add a permission.
Configure Azure AD B2C Sign Certificate

  • Select the My APIs tab, then select the IdentityExperienceFramework application.
Configure Azure AD B2C Sign Certificate

  • Under Permission, select the user_impersonation scope that you defined earlier.
  • Select Add permissions. As directed, wait a few minutes before proceeding to the next step.
Configure Azure AD B2C Sign Certificate

  • Select Grant admin consent for (your tenant name).
Configure Azure AD B2C Sign Certificate

  • Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the Cloud application administrator role.
  • Select Yes.
  • Select Refresh, and then verify that "Granted for ..." appears under Status for the scopes - offline_access, openid and user_impersonation. It might take a few minutes for the permissions to propagate.
Configure Azure AD B2C Sign Certificate

Register the Joomla Application:

  • Select App registrations, and then select New registration.
  • Enter a Name for the application such as: Joomla.
  • Under Supported account types, select Accounts in any organizational directory or any identity provider, for authenticating users with Azure AD B2C.
Configure Azure AD B2C Sign Certificate

  • Under Redirect URI, select Web, and then enter the ACS URL from the Service Provider Metadata tab of the miniOrange SAML plugin.
  • Select Register.
Configure Azure AD B2C Sign Certificate

  • Under Manage, click on Expose an API.
  • Click on Set for the Application ID URI and then click on Save, accepting the default value.
Configure Azure AD B2C Sign Certificate

  • Once saved, copy the Application ID URI and navigate to the Service Provider Metadata tab of the plugin.
Configure Azure AD B2C Sign Certificate

  • Paste the copied value under the SP Entity ID / Issuer field provided in this tab.
  • Click on Save.

Generate SSO Policies:

  • From our Azure B2C portal, navigate to the Overview section of your B2C tenant and record your tenant name. NOTE: If your B2C domain is b2ctest.onmicrosoft.com, then your tenant name is b2ctest.
Configure Azure AD B2C Sign Certificate

  • Enter your Azure B2C tenant name here, along with the application ID for IdentityExperienceFramework and ProxyIdentityExperienceFramework apps as registered in the above steps.
  • Then click on the Generate Azure B2C Policies button to download the SSO policies.
  • Extract the downloaded zip file. It contains the policy files and certificate (.pfx), which you will require in the following steps.

Setup Certificates:

NOTE: In the following step if the 'Identity Experience Framework' is not clickable then it might be the reason that you don't have an active Azure AD B2C subscription for that tenant. You can find the details regarding the Azure AD B2C subscription here and you can create a new tenant by following the steps here.


  • Sign in to the Azure portal and browse to your Azure AD B2C tenant.
Configure Azure AD B2C Sign Certificate

  • Under Policies, select Identity Experience Framework and then Policy keys.
Configure Azure AD B2C Sign Certificate

  • Select Add, and then select Options > Upload.
  • Enter the Name as SamlIdpCert. The prefix B2C_1A_ is automatically added to the name of your key.
Configure Azure AD B2C Sign Certificate

  • Using the upload file control, upload your certificate that was generated in the above steps along with the SSO policies (tenantname-cert.pfx).
  • Enter the certificate's password as your tenant name and click on Create. For example, if your tenant name is xyzb2c.onmicrosoft.com, enter the password as xyzb2c.
  • You should be able to see a new policy key with the name B2C_1A_SamlIdpCert.
  • On the overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
  • Select Policy Keys and then select Add.
  • For Options, choose Generate.
  • In Name, enter TokenSigningKeyContainer.
  • For Key type, select RSA.
  • For Key usage, select Signature.
Configure Azure AD B2C Sign Certificate

  • Select Create.
  • On the overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
  • For Options, choose Generate.
  • In Name, enter TokenEncryptionKeyContainer.
  • For Key type, select RSA.
  • For Key usage, select Encryption.
Configure Azure AD B2C Sign Certificate

  • Select Create.

Upload the Policies:

  • Select the Identity Experience Framework menu item in your B2C tenant in the Azure portal.
Configure Azure AD B2C Sign Certificate

  • Select Upload custom policy.
Configure Azure AD B2C Sign Certificate

  • As per the following order, upload the policy files downloaded in the above steps:
    • TrustFrameworkBase.xml
    • TrustFrameworkExtensions.xml
    • SignUpOrSignin.xml
    • ProfileEdit.xml
    • PasswordReset.xml
    • SignUpOrSigninSAML.xml
  • As you upload the files, Azure adds the prefix B2C_1A_ to each.

In Joomla SAML plugin, go to Service Provider Setup tab. There are three ways to configure the plugin:

A. By uploading IDP metadata:

  • In Joomla SAML plugin, go to Service Provider Setup tab, then click on Upload IdP Metadata.
Upload IdP Metadata

B. By Metadata URL:

  • Enter Metadata URL (Copy from IDP app) and click on Fetch button.
Upload IdP Metadata

C. Manual Configuration:

  • Copy SAML Entity ID, SAML Single-Sign-On Endpoint URL and X.509 certificate from Federation Metadata document and paste it in Idp Entity ID or Issuer, Single Sign-on URL, X.509 Certificate fields respectively in the plugin.
IdP Entity ID or Issuer SAML Entity ID in the Federation Metadata document
Single Sign-On URL SAML Single-Sign-On Endpoint URL in the Federation Metadata document
X.509 Certificate Value X.509 Certificate in the Federation Metadata document
Upload IdP Metadata
  • Attributes are user details that are stored in your Identity Provider.
  • Attribute Mapping helps you to get user attributes from your Identity Provider (IDP) and map them to Joomla user attributes like firstname, lastname, address, phone etc.
  • While auto registering the users in your Joomla site these attributes will automatically get mapped to your Joomla user details.
  • Go to Attribute Mapping tab and fill in all the fields.
Username: Name of the username attribute from IdP (Keep NameID by default)
Email: Name of the email attribute from IdP (Keep NameID by default)
Name: Name of the name attribute from IdP
Joomla Attribute Mapping
  • You can check the Test Configuration Results under Service Provider Setup tab to get a better idea of which values to map here.

Note: You can see how Attribute Mapping works here.

  • Group/Role mapping helps you to assign specific roles to users of a certain group in your Identity Provider (IdP).
  • While auto registering, the users are assigned roles based on the group they are mapped to.
Joomla Group Mapping
  • Group/Role mapping helps you to assign specific roles to users of a certain group in your Identity Provider (IdP).
  • While auto registering, the users are assigned roles based on the group they are mapped to.

Note: You can see how Group/Role Mapping works here.

  • Go to Login Settings tab. You can add login Url to Perform SAML SSO in your Joomla site by following the steps below.
  • There are multiple features available in this tab like Auto redirect the user to Identity Provider and Enable Backend Login for Super Users. To use these features, click on the respective checkboxes.
Joomla Group Mapping
  • Click on the Upgrade tab to check out our complete list of features and various licensing plans. OR you can click here to check features and licensing plans.
  • In case, you are facing some issue or have any question in mind, you can reach out to us by sending us your query through the Support button in the plugin or by sending us a mail at joomlasupport@xecurify.com.
More FAQs ➔

There are a couple of reasons why this can happen:

1. Caching is enabled on the website.
When auto-redirect is enabled, the user is redirected to the IDP login page and after logging in back to the main site but as caching is enabled it redirects to the IDP login page hence a loop.

2. HTTP/HTTPS discrepancy:
This happens when HTTPS is not enforced on the site but is configured on the IDP side with an HTTPS URL. This can be solved by enforcing HTTPS on the site by defining a redirect rule in the .htaccess file or at the Apache level.

3. Cookie adulteration:
The cookie created by the plugin after logging in the user is altered by another plugin which causes the user to not log in to the Joomla site but the session is created on IDP.

In Joomla SAML plugin, when an extension is not enabled after installing the plugin, after clicking on ‘Test Configuration’ it takes you to your own site instead of redirecting you to IDP. To resolve it, you need to enable all the extensions of the plugin after installing it.

Please follow the below steps to resolve this issue:

1. In the Joomla admin interface, go to Extensions -> Manage -> Manage.
2. Search for ‘miniorange’.
3. Enable all the extensions of the plugins.

Here are some frequent errors that can occur:

INVALID_ISSUER: This means that you have NOT entered the correct Issuer or Entity ID value provided by your Identity Provider. You’ll see in the error message what was the expected value (that you have configured) and what actually found in the SAML Response.
INVALID_AUDIENCE: This means that you have NOT configured Audience URL in your Identity Provider correctly. It must be set to https://base-url-of-your-joomla-site/plugins/authentication/miniorangesaml/ in your Identity Provider.
INVALID_DESTINATION: This means that you have NOT configured Destination URL in your Identity Provider correctly. It must be set to https://base-url-of-your-joomla-site/plugins/authentication/miniorangesaml/saml2/acs.php in your Identity Provider.
INVALID_SIGNATURE: This means that the certificate you provided did not match the certificate found in the SAML Response. Make sure you provide the same certificate that you downloaded from your IdP. If you have your IdP’s Metadata XML file then make sure you provide certificate enclosed in X509 Certificate tag which has an attribute use=’ signing’.
INVALID_CERTIFICATE: This means that the certificate you provided is not in a proper format. Make sure you have copied the entire certificate provided by your IdP. If copied from IdP’s Metadata XML file, make sure that you copied the entire value.

This is possible only when a certificate coming in SAML Response does not match with the certificate configured in the plugin. Copy the certificate value shown in the Test Configuration window and paste it in X.509 Certificate field in the Service Provider tab in the plugin.

Please follow the steps to the export configuration:
1) Go to the miniOrange SAML SP plugin and navigate to the Service Provider Setup tab.
2) Then click on the Import/Export button at the bottom of the page and then click on the Export Configuration button.
3) Navigate to System >> Manage and search miniOrange in the search bar. Then uninstall all miniOrange extensions.

Please follow the steps to import configuration:
1) Install the latest plugin and log in with your miniOrange credentials in the plugin.
2) Navigate to the Service Provider Setup tab and click on Import/Export button.
3) Upload the downloaded configuration file and then click on the Import Configuration button.

While updating Joomla SAML Plugin, if table or column is not added to the database then you will get a missing table error. This issue generally arises when a table or column is not added to the database while updating the plugin.
You can reinstall the plugin to resolve this issue, please follow the below steps:

Uninstall the existing plugin (Take the backup of the existing plugin before uninstalling the plugin)
– Go to Extensions -> Manage -> Manage
– Search for miniOrange
– Select all the extensions and click ‘Uninstall’.
Now install the plugin again and configure it.

A Joomla site can be either used as a Service Provider or an Identity Provider using the relevant SP or IDP plugin. You are facing this error probably because you have installed both the plugins on the same site.
In order to resolve this issue, please follow the below-mentioned steps: Delete the following folders from your Joomla directory:

1. /libraries/miniorangejoomlaidpplugin
2. /libraries/miniorangesamlplugin
3. /plugins/system/samlredirect
Now you should be able to log into your Joomla site.

Remove the remaining extensions:

1. In your Joomla site administrator console, go to Extensions -> Manage -> Manage.
2. Search for ‘miniorange’
3. Select all extensions and click Uninstall

The redirection issue occurs while using the Admin Tools plugin for Joomla SAML SSO, where the Admin Tools plugin makes changes in the .htaccess file and adds certain rules that prevent redirection from the site.

You can solve the above issue by following the steps given below:

1. Navigate to Admin tools >> Control Panel then click on the .htaccess maker option.
2. Then disable the option ‘Protect against common file injection attacks’.
Then clear the cache for your site and test for Single Sign-On.

SAML Tracer Logs:

1. Download SAML tracer add-on : Firefox: [ Link ] | Chrome:[ Link ] 2. Open the SAML tracer from the Browser toolbar.
3. Keep the SAML tracer window open.
4. Perform SSO/Test configuration and reproduce the issue.
5. Go to SAML tracer window.
6. You will get the option to Export SAML Tracer Log in a file (On top menu bar). Save the logs to a file, choose ‘None‘ when prompted and send us this file.

It seems that your Identity Provider is sending an error in the SAML Response. To troubleshoot this, please go to the Service Provider Setup tab of the SAML SP Plugin. Click on the Test Configuration and review the configuration result window. Ensure that the Attribute Mapping has been done correctly and verify that the X.509 Certificate Value is accurate.



ADFS_sso ×
Hello there!

Need Help? We are right here!

support