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

Pre-requisites : Download And Installation

• Download miniOrange ASP.NET SAML 2.0 Module.
• To set up the module, extract the file asp.net-saml-sso-module-xxx.zip. You will find a DLL named miniorange-saml-sso.dll, a configuration file named saml.config and an integration.md file which contains steps for adding the module into your application.
• Add miniorange-saml-sso.dll into your bin folder (where other DLL files for your application exist).
• Register minorangesamlsso module in your application according to the steps provided in the file named integration.md.
• Add the provided configuration file saml.config in the root directory of your application.
• After integration, open your browser and browse the connector dashboard with the URL below:
  https://<your-application-base-url>/?ssoaction=config
• If the registration page or login page pops up, you have successfully added the miniOrange SAML SSO connector to your application.

• Register or log in with your account by clicking the Register button to configure the module.

Steps to configure Shibboleth Single Sign-On (SSO) Login into ASP.NET

1. Add Shibboleth in ASP.NET SAML Module

• Go to Plugin settings section and Choose Shibboleth from the list.

• You will see the Service Provider Settings option, where you will get the service provider metadata. You can have three options to provide the metadata to your IDP. Keep the metadata handy as it will be required later to configure step 2.

2. Configure Shibboleth as Identity Provider

• In conf/idp.properties, uncomment and set 'idp.encryption.optional' to true.
     eg. idp.encryption.optional = true
• In conf/metadata-providers.xml, configure Service Provider like this

<MetadataProvider xmlns:samlmd="urn:oasis:
names:tc:SAML:2.0:metadata" 

  id="miniOrangeInLineEntity" xsi:type="InlineMetadata
Provider"
sortKey="1"> 

  <samlmd:EntityDescriptor ID="entity" entityID="<SP-EntityID / 
Issuer
from Service Provider Info tab in plugin.>" 

    validUntil="2020-09-06T04:13:32Z"> 

    <samlmd:SPSSODescriptor AuthnRequests
Signed="false"
WantAssertionsSigned="true" 

    protocolSupportEnumeration="urn:oasis:names:
tc:SAML:2.0:protocol">


      <samlmd:NameIDFormat> 

        urn:oasis:names:tc:SAML:
1.1:nameid-format:emailAddress


      </samlmd:NameIDFormat> 

    <samlmd:AssertionConsumerService
Binding="urn:oasis:names:tc:
SAML:2.0:bindings:HTTP-POST" 

    Location="<ACS (AssertionConsumerService) URL from 
Step1 of
the plugin under Identity Provider Tab.>" 

      index="1" /> 

    </samlmd:SPSSODescriptor> 

    </samlmd:EntityDescriptor> 

</MetadataProvider>

• In conf/saml-nameid.properties, uncomment and set default NameID as Email Address like this

idp.nameid.saml2.default=urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

• In conf/saml-nameid-xml, search for shibboleth.SAML2NameIDGenerators. Uncomment the shibboleth.SAML2AttributeSourcedGenerator bean and comment all other ref beans

<!-- SAML 2 NameID Generation --> 

<util:list id="shibboleth.SAML2NameIDGenerators"> 

  <!--<ref bean="shibboleth.SAML2TransientGenerator" /> --> 

  <!-->ref bean="shibboleth.SAML2PersistentGenerator" /> --> 

  <bean parent="shibboleth.SAML2AttributeSourcedGenerator" 

  p:format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" 

  p:attributeSourceIds="#{ {'email'} }" /> 

</util:list>
    

• Make sure you have defined AttributeDefinition in conf/attribute-resolver.xml.

<!-- Note: AttributeDefinitionid must be same as what
 you provided in
attributeSourceIds in conf/saml-nameid.xml --> 

<resolver:AttributeDefinitionxsi:type="ad:Simple"
 id="email"
sourceAttributeID="mail"> 

  <resolver:Dependency ref="ldapConnector" /> 

  <resolver:AttributeEncoderxsi:type="enc:SAML2String" 
name="email"
friendlyName="email" /> 

</resolver:AttributeDefinition > 



<resolver:DataConnector id="ldapConnector"
 xsi:type="dc:LDAPDirectory"
ldapURL="%{idp.authn.LDAP.ldapURL}" 

  baseDN="%{idp.authn.LDAP.baseDN}"
 principal="%{idp.authn.LDAP.bindDN}" 

  principalCredential="%{idp.authn.LDAP.bindDNCredential}"> 


  <dc:FilterTemplate> 

    <!-- Define you User Search Filter here --> 

    <![CDATA[
(&(objectclass=*)
(cn=$requestContext.principalName)) ]]> 

  </dc:FilterTemplate> 
 


  <dc:ReturnAttributes>*</dc:ReturnAttributes> 

</resolver:DataConnector>

• Make sure you have AttributeFilterPolicy defined in conf/attribute-filter.xml.

<afp:AttributeFilterPolicy id="ldapAttributes"> 

<afp:PolicyRequirementRulexsi:type="basic:ANY"/> 

  <afp:AttributeRuleattributeID="email"> 

    <afp:PermitValueRulexsi:type="basic:ANY"/> 

  </afp:AttributeRule> 

</afp:AttributeFilterPolicy> 

• Restart the Shibboleth server.
• You need to configure these endpoints in the ASP.NET SAML module .

IDP Entity ID	https://<your_domain>/idp/shibboleth
Single Login URL	https://<your_domain>/idp/profile/SAML2/Redirect/SSO
Single Logout URL	https://<your_domain>/idp/shibboleth
X.509 Certificate	The public key certificate of your Shibboleth server

• You have successfully configured Shibboleth as SAML IdP ( Identity Provider) for achieving Shibboleth SSO login into your ASP.NET application.

3. Configure ASP.NET SAML Module as Service Provider

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

• 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 Continue SSO Integration to continue further with the SSO Integration.

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

5. Integration Code

• You can also find the Integration code in the Integration Code tab in the module. Just copy-paste that code snippet wherever you want to access the user attributes.
• Note: All the mapped attributes will be stored in the session so that you can access them in your application.

6. Login Settings

• Use the following URL as a link in your application from where you want to perform SSO:
• https://<your-application-base-url>/?ssoaction=login
• For example you can use it as:
• <a href="https://<your-application-base-url>/?ssoaction=login">Login</a>

7. Logout Settings

• Use the following URL as a link in your application from where you want to perform SLO:
• https://<your-application-base-url>/?ssoaction=logout
• For example you can use it as:
• <a href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>

You can configure the DotNetNuke SAML 2.0 Single Sign-On (SSO) module with any Identity Provider such as ADFS, 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.

If you are looking to Single Sign-On into your sites with any SAML compliant Identity Provider then we have a separate solution for that. We do provide SSO solutions for the following:

Additional Resources

• Introduction to ASP.NET SAML Single Sign-On (SSO)
• Single Logout- How it works
• What is Single Sign-On (SSO) solution | How does it work?
• Single Sign-On (SSO) to an ASP.NET mvc application
• Setup Shibboleth as a SAML 2.0 Identity Provider
• Add Attribute in Shibboleth