Search Results :

×
Sign Up Contact Us

Contents

Guide to Configure ASP.NET Core SAML SSO using PingFederate as IDP

ASP.NET Core SAML Single Sign-On (SSO) middleware gives the ability to enable SAML Single Sign-On for your ASP.NET core applications. Using Single Sign-On you can use only one password to access your ASP.NET core application and services. Our middleware 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 ASP.NET Core and PingFederate considering PingFederate as IdP.

download plugin button Download plugin pricing button plugin pricing button Pricing Plans

Platform Support: The ASP.NET Core SAML middleware supports ASP.NET Core 2.0 and above. It supports all the ASP.NET Core platforms, including Windows, Linux and macOS.


NuGet Package
.NET CLI

PM> NuGet\Install-Package miniOrange.SAML.SSO


Note: To integrate the miniOrange ASP.NET SAML SSO middleware in your application, you will be required to add the below namespaces, services and middleware in your project, below is a sample implementation for reference.
Include only the highlighted section below in the Program.cs file of your application.

  using miniOrange.saml;
  using System.Reflection
  var builder=WebApplication.CreateBuilder(args);

  // Add services to the container.
  builder.Services.AddRazorPages();
  builder.Services.AddminiOrangeServices(Assembly.GetExecutingAssembly());

  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();

  #if NET9_0_OR_GREATER
  app.MapStaticAssets();
  #else
  app.UseStaticFiles();
  #endif

  app.UseminiOrangeSAMLSSOMiddleware();
  app.Run();
NuGet Packege
.NET CLI

PM> NuGet\Install-Package miniOrange.SAML.SSO


Note: To integrate the miniOrange ASP.NET SAML SSO middleware in your application, you will be required to add the below namespaces, services and middleware in your project, below here is a sample.
Include only the highlighted section below in the Program.cs file of your application.

  using miniOrange.saml;
  using System.Reflection;

  public class Startup
  {

    public Startup(IConfiguration configuration)
    {
      Configuration = configuration;
    }
    public IConfiguration Configuration { get; }

    // This method gets called by the runtime. Use this method to add services to the container.
    public void ConfigureServices(IServiceCollection services)
    {
      services.AddRazorPages();
      services.AddminiOrangeServices(Assembly.GetExecutingAssembly());
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
      if (env.IsDevelopment())
      {
        app.UseDeveloperExceptionPage();
      }
      else
      {
        app.UseExceptionHandler("/Error");
        // The default HSTS value is 30 days. You may want to change this for production scenarios, see         https://aka.ms/aspnetcore-hsts.
        app.UseHsts();
      }

      app.UseHttpsRedirection();

      app.UseCookiePolicy();
      app.UseAuthentication();

      #if NET9_0_OR_GREATER
      app.MapStaticAssets();
      #else
      app.UseStaticFiles();
      #endif

      app.UseminiOrangeSAMLSSOMiddleware();

      app.UseRouting();
      app.UseAuthorization();
      app.UseEndpoints(endpoints =>
      {
        endpoints.MapRazorPages();
      });
    }
  }
  • 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.
ASP.NET SSO Middleware Enterprise Plugin Download

  • 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:
dotnet nuget add source C:\miniOrangePackages--name miniOrangePackage
  • Open your Project in the terminal:
cd C:\Path\To\YourProject
  • Install the Package in your project using the below command:
dotnet add package miniOrange.SAML.SSO --source miniOrangePackage

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.
Nuget Package Manager

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

  • 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.
Package Sources Window

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

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

  • Note: To integrate the miniOrange ASP.NET SAML SSO middleware in your application, you will be required to add the below namespaces, services and middleware in your project, below is a sample implementation for reference.
    Include only the highlighted section below in the Program.cs file of your application.
  using miniOrange.saml;
  using System.Reflection
  var builder=WebApplication.CreateBuilder(args);

  // Add services to the container.
  builder.Services.AddRazorPages();
  builder.Services.AddminiOrangeServices(Assembly.GetExecutingAssembly());

  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();

  #if NET9_0_OR_GREATER
  app.MapStaticAssets();
  #else
  app.UseStaticFiles();
  #endif

  app.UseminiOrangeSAMLSSOMiddleware();
  app.Run();
  • 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.
ASP.NET SSO Middleware Enterprise Plugin Download

  • 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:
dotnet nuget add source C:\miniOrangePackages--name miniOrangePackage
  • Open your Project in the terminal:
cd C:\Path\To\YourProject
  • Install the Package in your project using the below command:
dotnet add package miniOrange.SAML.SSO --source miniOrangePackage

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.
Nuget Package Manager

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

  • 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.
Package Sources Window

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

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

  • Note: To integrate the miniOrange ASP.NET SAML SSO middleware in your application, you will be required to add the below namespaces, services and middleware in your project, below is a sample implementation for reference.
    Include only the highlighted section below in the Program.cs file of your application.
  using miniOrange.saml;
  using System.Reflection;

  public class Startup
  {

    public Startup(IConfiguration configuration)
    {
      Configuration = configuration;
    }
    public IConfiguration Configuration { get; }

    // This method gets called by the runtime. Use this method to add services to the container.
    public void ConfigureServices(IServiceCollection services)
    {
      services.AddRazorPages();
      services.AddminiOrangeServices(Assembly.GetExecutingAssembly());
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
      if (env.IsDevelopment())
      {
        app.UseDeveloperExceptionPage();
      }
      else
      {
        app.UseExceptionHandler("/Error");
        // The default HSTS value is 30 days. You may want to change this for production scenarios, see         https://aka.ms/aspnetcore-hsts.
        app.UseHsts();
      }

      app.UseHttpsRedirection();

      app.UseCookiePolicy();
      app.UseAuthentication();

      #if NET9_0_OR_GREATER
      app.MapStaticAssets();
      #else
      app.UseStaticFiles();
      #endif

      app.UseminiOrangeSAMLSSOMiddleware();

      app.UseRouting();
      app.UseAuthorization();
      app.UseEndpoints(endpoints =>
      {
        endpoints.MapRazorPages();
      });
    }
  }

Step by Step guide for ASP.NET Core SAML SSO using PingFederate as Identity Provider.

  • After integration, open your browser and browse the connector dashboard with the URL below:
 http(s)<your-dotnet-application-base-url>?ssoaction=config
  • If the registration page or login page pops up, you have successfully added the miniOrange SAML SSO middleware in your application.
ASP.NET Core- registeration page

  • Register or log in with your account by clicking the Register button to configure the middleware.
  • After successful registration, you will receive a trial license key on your registered email address.
  • To activate the middleware, you can either:
    • Enter the license key received via email in the provided input field.

    OR

    • Upload the license file that you downloaded by clicking on the Click Here button.
ASP.NET Middleware Verify Trial License

  • Then, check the box "I have read the above conditions and I want to activate the middleware", and click the Activate License button.
ASP.NET Middleware Activate License
  • After integration, open your browser and browse the connector 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 middleware in your application.
ASP.NET Core- login page

  • Log in with your licensed miniOrange account to configure the middleware.
  • 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.
License Activation

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

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:
ASP.NET Core- Service Provider Metadata

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:
ASP.NET Core- enter sp data manually

  • Login to your Ping Federate User Admin dashboard.
  • Click on the Identity Provider in the left navigation menu.
  • Under SP CONNECTION, click on Create New button.
Ping Federate User Admin dashboard

  • Select the Browser SSO Profiles connection template on the Connection Type tab and click Next.
Browser SSO Profiles

  • Select Browser SSO on the Connection Options tab and click Next.
PingFederate - Connection Options

  • Select File as the method for importing metadata and click Choose file to choose the miniOrange SSO plugin’s metadata on the Import Metadata tab. Click Next.
PingFederate - Import Metadata

  • Review the information on the Metadata Summary tab and click Next.
  • In the General Info tab ensure that the Service Provider’s Entity ID, Connection Name, and Base URL fields pre-populate based on the metadata. Click Next.
  • Navigate to the Browser SSO tab and click on the Configure Browser SSO. You will be redirected to Browser SSO Setup wizard.
    • Select the IdP-Initiated SSO and SP-Initiated SSO options on the SAML Profiles tab and click Next.
    SP and IDP initiated SSO

    • Enter your desired assertion validity time from on the Assertion Lifetime tab and click Next. By default, it is configured 5 minutes for both.
    • Navigate to the Assertion Creation and click on the Configure Assertion Creation. You will be redirected to the assertion creation setup wizard.
      • In the Identity Mapping tab select STANDARD and click Next.
      • Select a Subject Name Format for the SAML_SUBJECT on the Attribute Contract tab and click Next.
      • Click Map New Adapter Instance on the Authentication Source Mapping.
      Map New Adapter Instance

      • Select an Adapter Instance and click Next. The adapter must include the user’s email address.
      Adapter Instance

      • Select the Use only the adapter contract values in the SAML assertion option on the Mapping Method tab and click Next.
      • Select your adapter instance as the Source and the email as the Value on the Attribute Contract Fulfilment tab and click Next.
      Attribute Contract Fulfilment

      • (Optional) Select any authorization conditions you would like on the Issuance Criteria tab and click Next.
      • Click Done on the Summary.
      • Click Next on the Authentication Source Mapping tab.
      • Click Done on the Summary tab.
      • Click Next on the Assertion Creation.
  • Navigate to the Protocol Settings tab of the Browser SSO wizard and click on the Configure Protocol settings.
    • Select POST for Binding and specify the single sign-on endpoint URL in the Endpoint URL field on the Assertion Consumer Service URL Click Next.
    Assertion Consumer Service URL

    • Select POST on the Allowable SAML Bindings tab and click Next.
    • Select your desired signature policies for assertions on the Signature Policy tab and click Next.
    Signature Policy

    • Select your desired encryption policy for assertions on the Encryption Policy tab and click Next.
    • Click Done on the Protocol Settings Summary tab.
  • Navigate to the Credentials and click on the Configure Credentials. You will be redirected to the Credentials setup wizard.
    • Select the Signing Certificate to use with the Single Sign-On service and select Include the certificate in the signature element in the Digital Signature Settings tab. Click Done.
    Digital Signature Settings

    • Click Done on the Summary.
    • Click Next on the Credentials.
  • Select Active for the Connection Status on the Activation & Summary tab and click Save.
  • Now, navigate to the Ping Federate User Admin dashboardè Identity Provider.
  • Click Manage All under SP Connections.
  • Click Export Metadata for the desired service provider connection.
  • Click Export on the Export & Summary tab and click Done.
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:
ASP.NET Core Enterprise- Service Provider Metadata

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.
  • ou 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:
ASP.NET Core Enterprise - Upload sp data manually

  • Login to your Ping Federate User Admin dashboard.
  • Click on the Identity Provider in the left navigation menu.
  • Under SP CONNECTION, click on Create New button.
Ping Federate User Admin dashboard

  • Select the Browser SSO Profiles connection template on the Connection Type tab and click Next.
Browser SSO Profiles

  • Select Browser SSO on the Connection Options tab and click Next.
PingFederate - Connection Options

  • Select File as the method for importing metadata and click Choose file to choose the miniOrange SSO plugin’s metadata on the Import Metadata tab. Click Next.
PingFederate - Import Metadata

  • Review the information on the Metadata Summary tab and click Next.
  • In the General Info tab ensure that the Service Provider’s Entity ID, Connection Name, and Base URL fields pre-populate based on the metadata. Click Next.
  • Navigate to the Browser SSO tab and click on the Configure Browser SSO. You will be redirected to Browser SSO Setup wizard.
    • Select the IdP-Initiated SSO and SP-Initiated SSO options on the SAML Profiles tab and click Next.
    SP and IDP initiated SSO

    • Enter your desired assertion validity time from on the Assertion Lifetime tab and click Next. By default, it is configured 5 minutes for both.
    • Navigate to the Assertion Creation and click on the Configure Assertion Creation. You will be redirected to the assertion creation setup wizard.
      • In the Identity Mapping tab select STANDARD and click Next.
      • Select a Subject Name Format for the SAML_SUBJECT on the Attribute Contract tab and click Next.
      • Click Map New Adapter Instance on the Authentication Source Mapping.
      Map New Adapter Instance

      • Select an Adapter Instance and click Next. The adapter must include the user’s email address.
      Adapter Instance

      • Select the Use only the adapter contract values in the SAML assertion option on the Mapping Method tab and click Next.
      • Select your adapter instance as the Source and the email as the Value on the Attribute Contract Fulfilment tab and click Next.
      Attribute Contract Fulfilment

      • (Optional) Select any authorization conditions you would like on the Issuance Criteria tab and click Next.
      • Click Done on the Summary.
      • Click Next on the Authentication Source Mapping tab.
      • Click Done on the Summary tab.
      • Click Next on the Assertion Creation.
  • Navigate to the Protocol Settings tab of the Browser SSO wizard and click on the Configure Protocol settings.
    • Select POST for Binding and specify the single sign-on endpoint URL in the Endpoint URL field on the Assertion Consumer Service URL Click Next.
    Assertion Consumer Service URL

    • Select POST on the Allowable SAML Bindings tab and click Next.
    • Select your desired signature policies for assertions on the Signature Policy tab and click Next.
    Signature Policy

    • Select your desired encryption policy for assertions on the Encryption Policy tab and click Next.
    • Click Done on the Protocol Settings Summary tab.
  • Navigate to the Credentials and click on the Configure Credentials. You will be redirected to the Credentials setup wizard.
    • Select the Signing Certificate to use with the Single Sign-On service and select Include the certificate in the signature element in the Digital Signature Settings tab. Click Done.
    Digital Signature Settings

    • Click Done on the Summary.
    • Click Next on the Credentials.
  • Select Active for the Connection Status on the Activation & Summary tab and click Save.
  • Now, navigate to the Ping Federate User Admin dashboardè Identity Provider.
  • Click Manage All under SP Connections.
  • Click Export Metadata for the desired service provider connection.
  • Click Export on the Export & Summary tab and click Done.
  • Click on the Add new IDP button to configure a new Identity Provider.
ASP.NET Core SAML SSO using PingFederate as IDP - Add New IDP

  • Under the Plugin Settings tab, select PingFederate as your identity provider from the list shown.
ASP.NET Core SAML SSO using PingFederate as IDP - Add New IDP

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

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 middleware 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:
ASP.NET Core- Upload IDP Metadata

  • 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.
ASP.NET Core- Configure IDP Manually
  • Click on the Add new IDP button to configure a new Identity Provider.
ASP.NET Core SAML SSO using PingFederate as IDP - Add New IDP

  • Under the Plugin Settings tab, select PingFederate as your identity provider from the list shown.
Identity Provider List

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

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 middleware 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:
ASP.NET Coren Enterprise- Upload IDP Metadata

  • 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.
ASP.NET Core Enterprise- Configure IDP Manually
  • After uploading the metadata details, navigate to the Identity Provider Settings section. Hover over the Select Actions dropdown and click on Test Configuration.
ASP.NET Core- Test Configuration

  • The screenshot below shows a successful result. Click on SSO Integration to further continue with the SSO Integration.
ASP.NET Core- Test Configuration

  • If you are experiencing any error on the middleware end you’ll be shown with the window similar to below.
ASP.NET Core- Test Configuration Error

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

  • 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.
  • After uploading the metadata details, navigate to the Identity Provider Settings section. Hover over the Select Actions dropdown and click on Test Configuration.
ASP.NET Core Enterprise- Test Configuration

  • The screenshot below shows a successful test result. Please click on click here to complete the remaining SSO integration steps.
ASP.NET Core Enterprise - Test Configuration

  • If you are experiencing any error on the middleware end, click on the Troubleshooting button.
ASP.NET Core Enterprise - Troubleshoot

  • To troubleshoot the error, you can follow the below steps:
  • Under the Troubleshoot tab, enable the toggle to receive the plugin logs and reproduce the issue.
  • Download the log file by clicking on the Download Log File button to see what went wrong.
ASP.NET Core Enterprise - log file

  • 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 Middleware, click on Attribute/Role Mapping tab as shown in the image.
ASP.NET Core- Attribute Mapping

  • If you want to pass additional attributes from your IdP, enter the Attribute Name and corresponding Attribute Value under Custom Attribute Mapping.
  • 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.
ASP.NET Core- Attribute Mapping
  • 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 Middleware, 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.
ASP.NET Core Enterprise- Attribute Mapping

  • 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).
ASP.NET Core Enterprise - Custom Attribute Mapping

  • These claims correspond to the attributes sent by your Identity Provider (IdP).
ASP.NET Core Enterprise - Custom Attribute Mapping

  • 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.
ASP.NET Core Enterprise - Custom Attribute Multiple Mapping

  • The plugin 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 Vaue 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.
ASP.NET Core Enterprise - Role Mapping

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).
ASP.NET Core Enterprise - Domain Restriction

  • 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.
ASP.NET Core Enterprise - Domain Restriction Save Domains
  • 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 asp.net middleware application.
  • Just copy-paste that code snippet wherever you want to access the user attributes.
ASP.NET Core- Integration Code

  • Note: With the trial middleware the authenticated user details are stored in user claims using the default .NET Cookie Authentication. Support of setting user claims using Header-based, Session-based, JWT-based authentication is available in our 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;
  }
  • These steps allow you to retrieve the SSO user information in your application in the form of user claims.
  • Simply copy and paste the code snippet wherever you want to access the user attributes.
ASP.NET Core Enterprise- Integration Code

  • 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;
  }
  • Hover on Select Actions and click on Copy SSO Link.
ASP.NET Core Copy SSO Link

  • Use the following URL as a link in the application from where you want to perform SSO:
  https://<asp.net-middleware-base-url>/?ssoaction=login
  • For example, you can use it as:
  <a href="https://<asp.net-middleware-base-url>/?ssoaction=login">Log in</a>
  • Hover on Select Actions and click on Copy SSO Link.
ASP.NET Core Enterprise Copy SSO Link

  • Use the following URL as a link in the application from where you want to perform SSO:
  https://<asp.net-middleware-base-url>/?ssoaction=login
  • For example, you can use it as:
  <a href="https://<asp.net-middleware-base-url>/?ssoaction=login">Log in</a>
  • Use the following URL as a link to your application from where you want to perform SLO:
  https://<asp.net-middleware-base-url>/?ssoaction=logout
  • For example, you can use it as:
  <a href="https://<asp.net-middleware-base-url>/?ssoaction=logout">Log out</a>
  • Use the following URL as a link to your application from where you want to perform SLO:
  https://<asp.net-middleware-base-url>/?ssoaction=logout
  • For example, you can use it as:
  <a href="https://<asp.net-middleware-base-url>/?ssoaction=logout">Log out</a>

Advanced Settings

If you want to apply Advanced Settings, navigate to the Advanced Settings tab.

Auto Redirect to IdP
  • Enable the Auto Redirect to IdP toggle button to automatically redirect users to the configured Identity Provider during login.
  • Select the IDP where you want to redirect the users from the specific Url in the Default IDP dropdown.
  • Choose the Type of Redirection as Restricted or Public based on your requirement.
  • If required, enter the URLs that should be excluded from redirection in the Exclude URLs field, separated by commas.
  • Click on Save to store the configuration successfully.
ASP.NET Core Enterprise - Auto Redirection to Idp

Disable Admin Dashboard
  • Enable the Disable Admin Dashboard toggle to hide the miniOrange Admin Dashboard, and click on Save to apply the changes.
ASP.NET Core Enterprise - Disable Admin Dashboard

Certificate Information
  • Navigate to the Certificate Information section and select the required Certificate Type (Signing Certificate or Encryption Certificate).
  • Click on Regenerate Certificate if you want to generate a new certificate.
ASP.NET Core Enterprise - Certificate Information

  • Then click on Apply New Certificate to apply the updated certificate.
ASP.NET Core Enterprise - Certificate Information

Upload Custom Certificate
  • Navigate to the Upload Custom Certificate section and select the required Certificate Type (Signing Certificate or Encryption Certificate).
  • Click on Choose File to upload the Public Key (.crt) and Private Key (.pfx) files, and enter the Private Key Password in the provided field.
  • After providing the required details, click on Save to upload and apply the custom certificate successfully.
ASP.NET Core Enterprise - Upload Custom Certificate

Related Articles


 Thank you for your response. We will get back to you soon.

Something went wrong. Please submit your query again

We'll Reach Out to You at the Earliest!


ADFS_sso ×
Hello there!

Need Help? We are right here!

support