Moodle SAML Single Sign-On (SSO) using Azure B2C as IdP | Azure B2C SSO Login

Overview

SAML Single Sign-On (SSO) for your Moodle site can be achieved using our miniOrange SAML SSO plugin. Our plugin is compatible with all the SAML compliant Identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between Azure B2C as Identity Provider (IdP) and Moodle as Service Provider (SP).

Download Plugin Pricing Plans

Pre-requisites : Download And Installation

To configure Azure B2C as IdP with Moodle, you will need to install the miniOrange Moodle SAML 2.0 SSO plugin

Configuration Steps

1. Setup Azure B2C as IdP

Follow the steps below to configure Azure B2C as an Identity Provider:

Configure Azure B2C as IdP

• In the Plugins tab scroll to Service Provider Metadata section you can find the SP metadata such as SP Entity-ID and ACS (AssertionConsumerService) URL which are required to configure the Identity Provider.

Register the Identity Experience Framework application

• Login into Azure B2C Portal
• Click on the Azure AD B2C tenant.

• From the left tab section, navigate to App registrations >> New registration.

• For Name, enter IdentityExperienceFramework.
• In the Supported account types section, select Accounts in this organizational directory only.

• 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 here 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.
• Click on the Register button.

• Record the Application (client) ID for use in a later step.

Register the IdentityExperience Framework application

• In left side, under Manage section, click the Expose an API subtab.
• Click on Add a scope, then click Save and continue button to accept the default application ID URI.

• 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 IdentityExperience Framework
• Admin consent description: Allow the application to access IdentityExperience Framework on behalf of the signed-in user.
• Click Add scope to save the details.

Register the ProxyIdentityExperienceFramework application:

• Click on App registrations tab, and then select New registration.
• For Name, enter ProxyIdentityExperienceFramework.
• Under Supported account types, select Accounts in this organizational directory only.

• Under Redirect URI, use the drop-down to select Public client/native (mobile & desktop).
• For Redirect URI, enter myapp://auth.
• In the Permissions section, select the Grant admin consent to openid and offline_access permissions check box.
• Click on Register button.

• Record the Application (client) ID for use in a later step.

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

• In the left section, under Manage section, click on Authentication tab.
• Scroll down to Advanced settings section, enable Allow public client flows (select Yes).
• Click on Save button to save the changes.

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

• Under Manage section, click on API permissions tab.
• In the Configured permissions section, click on Add a permission.

• Click on the My APIs tab, then select the IdentityExperienceFramework application.

• Under the Permission section, select the user_impersonation scope that you defined earlier.
• Select Add permissions. As directed, wait a few minutes before proceeding to the next step.

• Click on Grant admin consent for (your tenant name).

• 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.
• Click on the Yes button.
• Click on Refresh.

• Verify that "Granted for ..." appears in Status column for the scopes - offline_access, openid and user_impersonation. It might take a few minutes for the permissions to propagate.

Register the moodle Application:

• Navigate to App registrations >> New registration.
• Enter a Name for the application such as: moodle.
• In Supported account types section, select Accounts in any identity provider or organizational directory (for authenticating users with user flows).

• In the Redirect URI section, select Web, and then enter the ACS URL from the Service Provider Metadata tab of the miniOrange SAML plugin.
• Enable the checkbox Grant admin consent to openid and offline_access permissions.
• Click on Register button.

• In the Manage section at left side, click on Expose an API tab.
• Click on Add for the Application ID URI and then click on Save, accepting the default value.

• Once saved, copy the Application ID URI and navigate to the Service Provider Metadata section of the plugin.

• Paste the copied value in the SP Entity ID / Issuer field.
• Scroll down and click on Save changes button.

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.

• Enter your Azure B2C tenant name below, along with the application ID for IdentityExperienceFramework and
  ProxyIdentityExperienceFramework apps as registered in the above steps.

• 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.

Upload the Certificate:

• Sign in to the Azure portal and browse to your Azure AD B2C tenant.
• In left seide, under Policies section, select Identity Experience Framework tab.

• Navigate to Policy keys >> Add.

• Select Options as Upload
• Enter the Name as SamlIdpCert. The prefix B2C_1A_ is automatically added to the name of your key.

• 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.

Create the signing key:

• On the Overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
• Select Policy Keys and then clik on Add.
• For Options field, choose Generate.
• In Name, enter TokenSigningKeyContainer.
• For Key type, select RSA.
• For Key usage, select Signature.

• Click on the Create button.

Create the encryption key

• On the overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
• Select Policy Keys and then click on Add.
• For Options, choose Generate.
• In Name, enter TokenEncryptionKeyContainer.
• For Key type, select RSA.
• For Key usage, select Encryption.

• Click on the Create button.

Upload the Policies:

• Select the Identity Experience Framework menu item in your B2C tenant in the Azure portal.

• Select Upload custom policy.

• 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.

You have successfully configured Azure B2C as SAML IdP (Identity Provider) for achieving moodle Azure B2C Single Sign-On (SSO) Login, ensuring secure login into moodle (WP) Site.

2. Configure Moodle as SP (Service Provider)

• Free
• Premium

In the miniOrange SAML SSO plugin, go to the Plugins tab. There are two ways to configure the plugin:

A. By uploading IDP metadata:

• Enter the IDP Name.
• In the Service Provider Setup section choose Metadata URL/XML from Select the Method dropdown.
• Copy and paste the IdP metadata URL or XML file in IDP Metadata URL/XML input field.
• Click on the Click here to Test the configuration.

B. Manual Configuration:

• Provide the required settings (i.e. IDP Name, IDP Entity-ID or Issuer, SAML Login URL, X.509 Certificate) as provided by your Identity Provider.
• Click on the Click here to Test the configuration.

Step 3: Attribute Mapping

• When the user performs SSO, the NameID value is sent by the Identity Provider. This value is unique for every user.
• For the plugin to access these attributes, assign the values for Username and Email as NameID.

In the miniOrange SAML SSO plugin, scroll down to the Service Provider Setup section of the plugin. There are two ways to configure the plugin:

A. By uploading IDP metadata:

• Provide any IDP Name. For example, my_IDP.
• Choose the value of Select the Method as Metadata URL/XML from dropdown.
• Enter the Metadata URL as
  https://tenant-name.b2clogin.com/tenant-name.onmicrosoft.com/B2C_1A_signup_signin_saml/Samlp/metadata

Note: You will need to replace the tenant-name in above URl with Azure B2C tenant name.

• Scroll to the bottom and click on Save changes button.

B. Manual Configuration:

• Provide the required settings (i.e. Identity Provider Name, IdP Entity ID or Issuer, SAML Login URL, X.509 Certificate) as provided by your Identity Provider.
• Click on the Save changes button to save your configuration.

Step 3: Attribute Mapping

Basic Attribute Mapping

• When the user performs SSO, the NameID value is sent by the Identity Provider. This value is unique for every user.
• For the plugin to access these attribute assign the Email and Username attribute.
• Addtionally user attributes can be mapped (such as Firstname and Lastname).
• Click on the Save changes button to save your configuration.

Custom Attribute Mapping

This feature allows you to map custom attribute sent by the IDP to the Moodle attributes.

• To create a custom attribute, navigate to Site Administration >> Users >> User Profile Fields in the plugin.
• Click on Create a new profile field , select the type of attribute from dropdown and enter the values in required fields.

• Assign the desired value to the created custom attribute.

• Scroll down and click on the Save changes button to save your configurations.

Step 4: Role Mapping

• In the free plugin, you can choose a default role that will be assigned to all the non-admin users when they perform SSO.

Note: Roles will be assigned to new users created by SSO. Existing Moodle users’ roles will not be affected.

• Scroll down to Role Mapping section.
• Select the Default Role and click on the Save changes button to save your configuration.

Step 4: Role Mapping

This feature allows you to assign and manage roles of the users when they perform SSO. Along with the default Moodle roles, this is compatible with any custom roles as well.

• Group/Role attribute will provide a mapping for the field name which contains role-related information sent by the IDP and will be used for Role Mapping.
• Scroll to the Role Mapping section and provide the mappings for the respective roles.
• Select the Default Role from the dropdown if the user role doesn't match with the assigned values.
• For example, If you have a user whose Group/Role attribute value is idp-teacher and you want to assign it to the teacher group then, just provide idp-teacher in the Teacher: field of Role mapping section.

Note: You can assign multiple values separated with semi-colon(;).

• Click on the Save changes button to save your configurations.

Step 5: SSO Settings

• In the plugin, you can add a login widget to enable SP-Initiated SSO on your site.
• Go to the Plugins >> Authentication >> Manage authentication.
• Click on the to enable the plugin visibility.
• Click on the ⬆ to set plugin preference.

Step 5: SSO settings

In the plugin you can add a login widget to enable SP-Initiated SSO on your site.

• Navigate to Site administrator >> Plugins >> Manage authentication.
• Click on the to enable the plugin visibility.
• Click on the ⬆ to set plugin preference.

• To enable auto-redirect from Moodle login page to WordPress site .
• Choose Yes value from the dropdown for Enable Auto-redirect to IDP from Moodle login page field.
• Note down Backdoor URL it will be useful when SSO fails.
• Click on the Save changes button to save your configuration.

You have successfully configured Moodle as SAML SP for achieving Azure B2C SSO login into your Moodle Site.

Related Articles

• Moodle Integrations and Plugins
• Moodle SAML Single Sign On
• Moodle SCIM and Remote User Sync

Why Our Customers choose miniOrange Moodle SAML Single Sign-On Solution?

24/7 Support

Get prompt support from our technical experts, accessible around the clock for direct assistance

 Sign Up

Affordable Pricing

miniorange provides most affordable Secure Moodle Single Sign-on Solutions.

 Pricing

Documentation

Get access to our detailed knowledge base, which includes comprehensive guides and instructional videos.

 Know More

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)    samlsupport@xecurify.com