ADFS (Active Directory Federation Services) Single Sign-On (SSO) login for Magento [SAML] can be achieved by using our Magento SAML SP Single Sign-On (SSO) plugin. Our SSO solution will make Magento a SAML 2.0 compliant Service Provider, allowing users to securely authenticate and login to the Magento site using ADFS. Our Magento Single Sign-On (SSO) solution helps to secure Magento sites behind the SSO login so that users are authenticated using their ADFS credentials. Seamless support for advanced SSO features like Attribute / Custom Mapping, Role Mapping etc.

Here we will go through a guide to configure SAML Single Sign-On SSO login between Magento site and ADFS by considering ADFS as IdP (Identity Provider) and Magento as SP (Service Provider). Our SSO plugin provides Unlimited user authentications from ADFS (Active Directory Federation Services). To know more about other features we provide in you Magento SAML Single Sign-On (SSO) plugin, you can click here.

SAML Single Sign On – SAML SSO Login

By miniOrange

Magento Single Sign On SSO login with Azure AD, Azure B2C, ADFS, Okta, Keycloak, Salesforce, Ping, Bitium, Gsuite, Shibboleth & many SAML IdPs [24/7 SUPPORT]

 Tested with 2.4.5

Get this plugin

Steps to configure ADFS SAML Single Sign-On (SSO) Login into Magento

1. Setup ADFS as IdP (Identity Provider)

Follow the steps below to configure ADFS as IdP for Magento

 Configure ADFS as IdP

• In the Magento SAML SP SSO plugin, navigate to Service Provider Metadata tab. In this tab you will find the SP metadata such as SP Entity ID and ACS (AssertionConsumerService) URL which are required to configure ADFS as the Identity Provider.

• On ADFS, search for ADFS Management application.

• Select Relying Party Trust and then Add Relying Party Trust after launching AD FS Management.

• From the Relying Party Trust Wizard, click the Start button. But first, make sure that Claims aware is selected.

• Add a relying party trust by selecting the appropriate options.

 Using Metadata URL

• In Select Data Source: Import data about the relying party from the internet or a local network, and then add the URL to the Federation metadata address. (To obtain the SP Meatadata URL, go to the Service Provider Info tab of the plugin).

• Skip step-5 to step-8 & start configuring from step-9.

 Using Metadata XML file

• In Select Data Source: Import data about the relying party from a file option & then browse the metadata file(You can download the SP metadata file from the plugin under the Service Provider Metadata tab).

• Skip step-5 to step-8 & start configuring from step-9.

 Using Manual configuration

• In Select Data Source: Enter Data about the relying party manually & Click on Next.

• Enter Display Name & Click Next.
• Upload the certificate & Click Next. Download the certificate from the plugin and upload it to ADFS.
• Select Enable support for the SAML 2.0 WebSSO protocol & Enter ACS URL from the plugins Service Provider Info Tab. Click Next.

• Add Entity ID as Relying party trust identifier from the plugin's Service Provider Info Tab, then click Add and Next.

• Also, download the Signing certificate from Service Provider Info Tab from the plugin.
• Click Next after selecting Permit everyone as an Access Control Policy.

• Click the Next button from Ready to Add Trust and click on the Close button.
• The list of Relying Party Trusts will be displayed. Click Edit Claim Issuance Policy after selecting the appropriate application.

• Click on Add Rule button.

• Click Next after selecting Send LDAP Attributes as Claims.

• Enter the following details & click on Finish.

Claim rule name:	Attributes
Attribute Store:	Active Directory
LDAP Attribute:	E-Mail-Addresses
Outgoing Claim Type:	Name ID


• Click Apply and then click on Ok button.
• Select property of the application & add the certificate downloaded from the add-on.


* Windows SSO (optional)

  Steps to configure ADFS for Windows Authentication

• Open elevated Command Prompt on the ADFS Server and execute the following command on it:

setspn -a HTTP/##ADFS Server FQDN## ##Domain Service Account##

FQDN is Fully Qualified Domain Name (Example : adfs4.example.com)

Domain Service Account is the username of the account in AD.

Example : setspn -a HTTP/adfs.example.com username/domain

• Go to the Authentication Policies area of the AD FS Management Console and update the Global Authentication Policies. In the Intranet zone, check Windows Authentication.

• Open Internet Explorer. Navigate to Security tab in Internet Options.
• Add the FQDN of AD FS to the list of sites in Local Intranet and then restart the browser.
• Select Custom Level for the Security Zone. Select Automatic Logon only in Intranet Zone from the list of options.

• Open the powershell and execute following two commands to enable windows authentication in Chrome browser.

Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Chrome")

Get-AdfsProperties | Select -ExpandProperty WIASupportedUserAgents

• You have configured ADFS for Windows Authentication. Now to add Relying Party for your Magento site you can follow these steps.

In this Guide, you have successfully configured ADFS SAML Single Sign-On (ADFS SSO Login) choosing ADFS as IdP and Magento as SP using Magento SAML Sigle Sign-On (SSO) Login plugin .This solution ensures that you are ready to roll out secure access to your Magento site using ADFS login credentials within minutes.

Additional Resources

• What is Single Sign-On (SSO) Login?
• What is ADFS?
• Configure LDAP attributes as claims for attribute mapping
• Magento SAML Single Sign On (SSO) Plugin.