Guide to Configure ASP.NET Framework SAML SSO using Azure AD(Entra ID) as IDP

Pre-requisites : Download And Installation

A] NuGet Installation:

• Login to http://portal.miniorange.com/ and navigate to the Downloads tab. From there, locate your purchased plugin and click on Download Plugin to download the plugin zip file.

• Extract the Downloaded zip file in your machine and place the nuget package file (.nupkg file) in a some folder like "C:\miniOrangePackages"
• Run the following command in your VS terminal to add it as a package source:

• Open your Project in the terminal:

• Install the Package in your project using the below command:

OR

• After placing the NuGet package (.nupkg file) in a local folder, instead of using the terminal, you can also install it using Visual Studio by following the steps below:
• Open your .NET application in Visual Studio, click on Tools in the top navigation bar, and navigate to NuGet Package Manager → Manage NuGet Packages for Solution.

• A new window will open; click on the gear icon next to the Package source dropdown.

• A pop-up window will open; select Package Sources from the left navigation panel, click on the plus (+) icon, enter a name for the package source, provide the path of the folder where you placed the NuGet package in the Source field, then click Update and finally click OK to save the changes, as shown in the image.

• After closing the pop-up window, select the newly added package source from the Package source dropdown.

• Now click on the Browse tab, search for miniOrange.SAML.SSO, select the package from the results, and click Install.

B] Manual Installation:

• Extract the downloaded package from the miniOrange portal. It contains a Manual Installation folder with miniorange-saml-sso.dll and other DLL files which are required to be placed in your application's bin folder.
• Place the saml.config file and the miniOrangeContent folder in the root directory of your application.
• Register the miniOrange module in your web.config by following the steps in the integration.md.

Access the Module Dashboard

• After Installation, open your browser and browse the module dashboard with the URL below:
  

 http(s)<your-dotnet-application-base-url>?ssoaction=config


• If the login page pops up, you have successfully added the miniOrange SAML SSO module in your application.

• Log in with your licensed miniOrange account to configure the module.
• After logging in, the Account Setup dashboard will open. Enter the license key to activate the plugin, which you will receive after logging in to portal.miniorange.com and navigating to Manage License → License Keys.

• Then, check the box "I have read the above two conditions and I want to activate the plugin", and click the Activate License button.

A] Using SAML metadata URL or metadata file

• In the Plugin Settings menu, look for Service Provider Settings. Under that, you can find the metadata URL as well as the option to download the SAML metadata.

• Copy metadata URL or download the metadata file to configure the same on your identity provider end.

• You may refer to the screenshot below:

B] Uploading metadata manually

• From the Service Provider Settings section, you can manually copy the service provider metadata like SP Entity ID, ACS URL, Single Logout URL, and share it with your Identity Provider for configuration.
• You can also download the SP Certificate by clicking on Download SP Cert and provide it to your Identity Provider if required.
• Under the Encryption Certificate section, select the appropriate certificate type as per your requirement.
• After completing the above steps, click on Save to apply the configuration.

• You may refer to the screenshot below:

Steps to Configure Azure AD IdP

• Log in to Azure AD Portal.

• Select Azure Active Directory.

• Select Enterprise Application.

• Click on New Application.

• Click on Create your own Application.

• Enter the name for your app, then select Non-gallery application section and click on Create button.

• Click on Setup Single sign-on.

• Select the SAML tab.

• After clicking on Edit, enter the SP Entity ID for Identifier and the ACS URL for Reply URL from Service Provider Metadata tab of the plugin as per Step 1B.

• By default, the following Attributes will be sent in the SAML response. You can view or edit the claims sent in the SAML response to the application under the Attributes tab.

• Copy the App Federation Metadata Url to get the Endpoints required for configuring your Service Provider.

• Assign users and groups to your SAML application
  • Navigate to Users and groups tab and click on Add user/group.
  
  
  
  • Click on Users to assign the required user and then click on select.
  
  
  
  • You can also assign a role to your application under Select Role section.

You have successfully configured Microsoft Entra ID (formerly Azure AD) as SAML IDP (Identity Provider) for achieving ASP.NET Framework Single Sign-On (SSO).

• Click on the Add new IDP button to configure a new Identity Provider.

• Under the Plugin Settings tab, select Azure AD as your identity provider from the list shown.

There are two ways detailed below with which you can configure your SAML Identity Provider metadata in the module.

A] Upload metadata using the Upload IDP Metadata button:

• If your identity provider has provided you with the metadata URL or metadata file (.xml format only), then you can simply configure the identity provider metadata in the module using the Upload IDP Metadata option.

• Copy metadata URL or download the metadata file to configure the same on your identity provider end.

• You may refer to the screenshot below:

• You can choose any one of the options according to the metadata format you have available.

B] Configure the identity provider metadata manually:

• After configuring your Identity Provider, it will provide you with IDP Entity ID, IDP Single Sign On URL and SAML X509 Certificate fields respectively.

• Click Save to save your IDP details.

• After uploading the metadata details, navigate to the Identity Provider Settings section. Hover over the Select Actions dropdown and click on Test Configuration.

• The screenshot below shows a successful test result. Please click on click here to complete the remaining SSO integration steps.

• If you are experiencing any error on the module end you'll be shown with the window similar to below.

• To troubleshoot the error you can follow the below steps:
• Under Troubleshoot tab, enable the toggle to receive the plugin logs.

• Once enabled, you will be able to retrieve plugin logs by navigating to Plugin Settings tab and clicking on Test Configuration.
• Download the log file from the Troubleshoot tab to see what went wrong.
• You can share the log file with us at aspnetsupport@xecurify.com and our team will reach out to you to resolve your issue.

• After testing the configuration, Map your application attributes with the Identity Provider (IdP) attributes.

• From the left-hand menu of the miniOrange ASP.NET SAML SSO Module, click on Attribute/Role Mapping tab as shown in the image.
• Map the required IdP attributes (such as Username, Email, Firstname, and Lastname) received in the SAML Response to their corresponding fields.

• Note: All the mapped attributes will be stored in the session so that you can access them in your application.
• Once the attributes are mapped, click Save Attribute Mapping to apply changes.

Custom Attribute Mapping

• If you want to pass additional attributes from your IdP, enter the Attribute Name and corresponding Attribute Value under Custom Attribute Mapping.
• From the Attribute Value (Claim) dropdown, select one of the claims you received in the Test Configuration results. For example: NameID.
• These claims correspond to the attributes sent by your Identity Provider (IdP).

• These claims correspond to the attributes sent by your Identity Provider (IdP).

• In the Attribute Name field, enter the name of the attribute as you want it to appear or be used in your .NET application.
• You can add multiple mappings if your application requires multiple attributes by clicking on the + button.
• After defining all the required mappings, click on Save Attribute Mapping to store the configuration.

• The module will now translate the incoming SSO claims from your Identity Provider (IdP) into the custom attribute names defined here.

Role Mapping

• In the Role Mapping section, enter the Group Attribute Name exactly as configured in your Identity Provider to fetch the user group information.
• Enter the Role Name received from the Identity Provider and map it to the appropriate Role Value field. In the Role Value field, enter the roles defined in your .NET application.
• For example: Map the IdP group Group1 or Group10 received under the UserGroups attribute to the corresponding role configured in your .NET application.
• After adding the required mappings, click on Save Role Mapping to save the configuration successfully.

Domain Restriction

• This feature can be used to restrict user access to the site based on the domain of their mapped "Email" Attribute.
• In the Email Attribute field, enter the attribute name that contains the user's email address as received from your Identity Provider (IdP).

• In the Domain Name field, enter the domain(s) you want to allow or restrict, separated by commas if adding multiple domains.
• Enable the Restrict toggle based on your requirement to configure blacklist or whitelist access.
• After completing the configuration, click on Save Domains to save the settings successfully.

• These steps allow you to retrieve the SSO user information in your application in the form of session.
• You can also look the setup tour to understand how the SSO integration would work in your asp.net module application.
• Just copy-paste that code snippet wherever you want to access the user attributes.

• Hover on Select Actions and click on Copy SSO Link.

• Use the following URL as a link in the application from where you want to perform SSO:

• For example, you can use it as:

• Use the following URL as a link to your application from where you want to perform SLO:

• For example, you can use it as: