• Home
• Login with External IDP
• Shibboleth Single Sign-On

Configure Shibboleth as an Identity Provider for SSO

---

Configure Shibboleth as a Identity Provider (IdP) for Single Sign-On (SSO) into your applications, enabling users to authenticate themselves across multiple applications using their existing Shibboleth credentials without needing to sign in again.

In this setup, Shibboleth acts as the Identity Provider (IdP), miniOrange acts as a broker, and other applications act as Service Providers (SPs). This setup eliminates the need to manage different identities as all information is stored in a unified location - Shibboleth, simplifying the integration process and enhancing overall security.

Additionally, miniOrange's Identity Broker solution facilitates cross-protocol authentication , allowing the user to authenticate using Shibboleth SAML protocol and obtain access to the application, which supports SAML, OAuth and other protocols. This demonstrates how miniOrange Identity brokering enables users to authenticate across different protocols, improving the flexibility and interoperability of SSO solutions.

Follow the easy steps given in this guide to login using Shibboleth.

Follow the Step-by-Step Guide given below for Shibboleth Single Sign-On (SSO)

1. Configuring miniOrange as Service Provider (SP) in Shibboleth

• In conf/idpproperties, uncomment and set 'idp.encryption.optionaI' 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="miniOrangeInLineEntitInlineMetadataProvider" sortKey="1"> 

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

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

         <samlmd:SPSSODescriptor AuthnRequestsSigned="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 IDP Tab.>" 

          &nby" xsi:type="sp;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.

2. Configure Shibboleth as Identity Provider (IDP) in miniOrange

• Go to miniOrange Admin Console .
• From the left navigation bar select Identity Provider.
• Click on Add Identity Provider button.



• Select SAML. Click on Import IDP metadata.



• Enter Shibboleth as IDP name and click on Save.
• You can also provide the details manually. You need to configure following endpoints:

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.

• Click Save

3. Test Connection

• Visit your Login Page URL.
• Go to Identity Providers tab.
• Click on Select >> Test Connection option against the Identity Provider (IDP) you configured.



• On entering valid Shibboleth credentials (credentials of user assigned to app created in Shibboleth), you will see a pop-up window which is shown in the below screen.



• Hence your configuration of Shibboleth as IDP in miniOrange is successfully completed.

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.

• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP

• To add your users in miniOrange there are 2 ways:

1. Create User in miniOrange

2. Bulk Upload Users

1. Create User in miniOrange

• Click on Users >> User List >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on Onboarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.

2. Bulk Upload Users in miniOrange via Uploading CSV File.

• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

• Click on External Directories >> Add Directory in the left menu of the dashboard.



• Select Directory type as AD/LDAP.



1. STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
2. STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway in your premise.




• Enter LDAP Display Name and LDAP Identifier name.
• Select Directory Type as Active Directory.
• Enter the LDAP Server URL or IP Address against LDAP Server URL field.
• Click on Test Connection button to verify if you have made a successful connection with your LDAP server.



• In Active Directory, go to the properties of user containers/OU's and search for Distinguished Name attribute.



• Enter the valid Bind account Password.
• Click on Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



• Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



• Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Allow users to change password	This allows your users to change their password. It updates the new credentials in your LDAP server
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Send Configured Attributes	If you enable this option, then only the attributes configured below will be sent in attributes at the time of login



• Click on Save. After this, it will show you the list of User stores. Click on Test Connection to check whether you have enter valid details. For that, it will ask for username and password.



• On Successful connection with LDAP Server, a success message is shown.
• Click on Test Attribute Mapping.



• Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.



• After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.

Refer our guide to setup LDAPS on windows server.

User Import and Provisioning from AD

• Go to Settings >> Product Settings in the Customer Admin Account.



• Enable the "Enable User Auto Registration" option and click Save.



• (Optional) To send a welcome email to all the end users that will be imported, enable the "Enable sending Welcome Emails after user registration" option and click Save.



• From the Left-Side menu of the dashboard select Provisioning.



• In Setup Provisioning tab select Active Directory in the Select Application drop-down.
• Toggle the Import Users tab, click on Save button.



• On the same section, switch to Import Users section.
• Select Active Directory from the dropdown and click on the Import Users tab, to import all the users from Active Directory to miniOrange.



• You can view all the Users you have imports by selecting Users >> User List from Left Panel.



• All the imported users will be auto registered.
• These groups will be helpful in adding multiple 2FA policies on the applications.

miniOrange integrates with various external user sources such as directories, identity providers, and etc.

• Okta
• ADFS
• Ping
• AWS Cognito
• Many more

Not able to find your IdP or Need help setting it up?

Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with Shibboleth

A. Restricting access to Shibboleth with IP Blocking

You can use adaptive authentication with Shibboleth Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way:

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.





Action for behavior Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

C. Add Adaptive Authentication policy to Shibboleth.

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on save.

D.Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

• Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.






• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.




• In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
• In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” text box.


How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Configure Google Workspace as an Identity Provider for SSO
• Login using Keycloak as SAML Identity Provider
• SSO for apps using OKTA as SAML Identity Provider
• Configure ADFS as an Identity Provider for SSO
• Know more about Oracle EBS Shibboleth SSO Integration