Blazor SAML SSO with Azure AD as IDP
Blazor SAML Single Sign-On (SSO) application gives the ability to enable SAML Single Sign-On for your Blazor applications. Using Single Sign-On you can use only one password to access your Blazor application and services. Our application 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 Blazor and Microsoft Entra ID (formerly Azure AD) considering Azure AD as IdP. To know more about the features we provide for Blazor SSO, click here.
Steps to configure Blazor Single Sign-On (SSO) using Azure AD as IDP
Step 1: Pre-requisites: Download And Installation
- Install the Blazor SAML SSO Middleware in your application package using the nuget package
using miniorange.saml
public class Startup
{
public void ConfigureServices(IServiceCollection services)
{
services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme).AddCookie();
services.AddControllersWithViews();
}
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
app.UseHttpsRedirection();
app.UseRouting();
app.UseAuthorization();
app.MapRazorPages();
app.UseCookiePolicy();
app.UseAuthentication();
app.UseStaticFiles();
app.UseminiOrangeSAMLSSOMiddleware();
app.Run();
}
}
using Microsoft.AspNetCore.Authentication.Cookies;
using miniOrange.saml;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddRazorPages();
// Add authentication services
builder.Services.AddControllersWithViews();
builder.Services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme).AddCookie();
var app = builder.Build();
if (!app.Environment.IsDevelopment())
{
app.UseExceptionHandler("/Error");
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseRouting();
app.UseAuthorization();
app.MapRazorPages();
app.UseCookiePolicy();
app.UseAuthentication();
app.UseStaticFiles();
app.UseminiOrangeSAMLSSOMiddleware();
app.Run();
-
After integration, open your browser and browse the connector dashboard with
the URL below:
https://<blazor-application-base-url>/?ssoaction=config - If the registration page or login page pops up, you have successfully added the miniOrange ASP.NET SAML SSO connector to your application.
- Register or log in with your account by clicking the Register button to configure the application.
2. Configure Azure AD as 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 get the SAML SP metadata to configure onto your identity provider end.
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 may refer to the screenshot below:
- 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.
- 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 Blazor Single Sign-On (SSO).
- Log in to Azure AD Portal as admin
- Select Azure Active Directory.
- Select App registrations.
- Click on New registration.
- Assign a Name and choose the account type.
- In the Redirect URL field, provide the ACS URL provided in Service Provider Metadata tab of the plugin and click on Register button.
- Navigate to Expose an API from left menu panel.
- Click the Set button and replace the APPLICATION ID URL with the plugin's SP Entity ID.
- Go back to Azure Active Directory ⇒ App Registrations window and click on Endpoints.
- This will navigate up to a window with multiple URLs.
- Copy the Federation Metadata document URL to get the Endpoints required for configuring your Service Provider.
NOTE: Please ensure that the SP Entity ID value from the Service Provider Metadata tab doesn't have a trailing slash('/'). If SP Entity ID has a trailing slash then update it by removing the trailing slash from the SP EntityID / Issuer field under the Service Provider Metadata tab of the plugin, enter the updated value at Azure and click on the Save button.
You have successfully configured Microsoft Entra ID (formerly Azure AD) as SAML IdP ( Identity Provider) for achieving Azure AD SSO login into your Blazor application.
3. Configure Blazor SAML application as Service Provider
There are two ways detailed below with which you can configure your SAML identity provider metadata in the application.
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 application using the Upload IDP Metadata option.
- 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.
4. Testing SAML SSO
- Click on the Test Configuration button to test whether the SAML Configuration you’ve done is correct.
- The screenshot below shows a successful result. Click on SSO Integration to further continue with the SSO Integration.
- If you are experiencing any error on the application 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.
5. Attribute Mapping
- After testing the configuration, Map your application attributes with the Identity Provider (IdP) attributes.
- In free plugin you can configure only NameID
- Note: All the mapped attributes will be stored in the claims so that you can access them in your application.
6. Integration Code
- This steps allow you to retrieve the SSO user information in your application in the form of user claims.
- You can also look the setup tour to understand how the SSO integration would work in your Blazor application.
- Just copy-paste that code snippet wherever you want to access the user attributes.
- Note:This trial middleware only supports user information in claims, retrieving user information in session and headers is available in the premium plugin
- You can also copy the integration code from below:
string name=""; string claimtype=""; string claimvalue=""; if(User.Identity.IsAuthenticated) { foreach( var claim in User.Claims) { claimtype = claim.Type; claimvalue = claim.Value; } retrive custom attributes(for eg. Retrieve Mapped 'mobileNumber' attribute of your IDP) var identity = (ClaimsIdentity)User.Identity; IEnumerable claims = identity.Claims; string mobileNumber = identity.FindFirst("mobileNumber")?.Value; }
7. Login Settings
- 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:
https://blazor-application-base-url/?ssoaction=login -
For example, you can use it as:
<a href=”https://blazor-application-base-url/?ssoaction=login”>Log in</a>
8. Logout Settings
-
Use the following URL as a link to your application from where you want
to perform SLO:
https://blazor-application-base-url/?ssoaction=logout -
For example, you can use it as:
<a href=”https://blazor-application-base-url/?ssoaction=logout”>Log out</a>
You can configure the Blazor SAML 2.0 Single Sign-On (SSO) application with any Identity Provider such as ADFS, Microsoft Entra ID (formerly Azure AD), Bitium, Centrify, G Suite, JBoss Keycloak, Okta, OneLogin, Salesforce, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne, RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with your own custom identity provider. Check the list of identity providers here.
Additional Resources
- DNN SAML Single Sign-On (SSO)
- Umbraco SAML Single Sign-On (SSO)
- ASP.NET SAML Single Sign-On (SSO)
- Web3 login for ASP.NET Applications
- nopCommerce SAML Single Sign-On (SSO)
- DNN REST API Authentication
Need Help?
Not able to find your identity provider? Mail us on aspnetsupport@xecurify.com and we'll help you set up SSO with your IDP and for quick guidance (via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.
Need Help? We are right here!
