Shibboleth3 Single Sign On (SSO) for Your Application

Shibboleth Single Sign On (SSO) for Your Application miniOrange provides a ready to use solution for Your application. This solution ensures that you are ready to roll out secure access to your application using Shibboleth within minutes.

Step 1: Configuring miniOrange as Service Provider (SP) in Shibboleth3.

  • 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="miniOrangeInLineEntity" xsi:type="InlineMetadataProvider" 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.>"
           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.

Step 2: Configure Shibboleth3 as Identity Provider (IDP) in miniOrange

  • Go to miniOrange Admin Console.
  • From the left navigation bar select Identity Provider.
  • Shibboleth3 Saml App
  • Select SAML. Click on Import IDP metadata and browse for the file downloaded in step 1.
  • Shibboleth3 Saml App
  • Choose appropriate 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.

Step 3: Test Connection

  • Go to Identity Providers tab.
  • Click on Select>>Test Connection option against the Identity Provider you configured.
  • Shibboleth3-IDP-TestConnection
  • On entering valid Shibboleth3 credentials you will see a pop-up window which as shown in below screen.
  • SucessTestConn-Shibboleth3-IDP
  • Hence your configuration of Shibboleth3 as IDP in miniOrange is sucesssfully completed.

Step 4: Configure Your application in miniOrange

With us, You can configure application according to the the protocol it supports like SAML, OAuth, JWT, Ws-fed etc.


  • For example lets say the application supports SAML. Then go with the configurations Shown in SAML Application Tab.
  • Login to miniOrange Admin Console.
  • Go to Apps >> Manage Apps Click Configure Apps button.
  • azure ad saml Apps
  • Then click on SAML tab. Search for Custom App.

  • azure ad saml Apps azure ad saml Apps
  • Get the ACS URL and SP Entity ID from your application.

  • Enter the following values OR click on Import SP Metadata:

  • Service Provider Name Choose appropriate name according to your choice
    SP Entity ID or Issuer Your Application Entity ID
    ACS URL X.509 Certificate (optional) Your Application Assertion Consumer Service URL
    NameID Format  Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
    Response Signed Unchecked
    Assertion Signed Checked
    Encrypted Assertion Unchecked
    Group policy Default
    Login Method

  • Click on Save to configure Your applcation.
  • Now to get the IDP metadata of the app configured, Go to apps >> your_app >> select >> metadata tab.

  • azure ad saml Apps
  • Click on the Show Metadata details in the Information required to Authenticate via External IDPs section. Download the metadata XML file by clicking on Download Metadata button or copy the Metadata URL link.
  • azure ad saml Apps
  • You need to Upload this metadata in your application.
  • To configure OAuth application in miniOrange, login to miniOrange Admin Console.

  • Go to Apps >> Manage Apps Click Configure Apps button.

  • configure app
  • Select on OAuth/OIDC tab. Click on Open ID Connect App .

  • You can add any OAuth Client app here to enable miniOrange as OAuth Server. Few popular OAuth client apps for single sign-on are Salesforce, WordPress, Joomla, Atlassian, etc.

  • OAuth openIDConnect app OAth AddopenIDConnect app
  • Enter following Values:
  • Client Name Add appropriate Name
    Redirect URL Get the Redirect-URL from your OAuth Client
    Descrption Add if required
    Group Name Default
    Policy Name
    Login Method

  • Click on Save

  • Now to provide the required data to OAuth client go to the app configured i.e apps >> your_app >> select >> edit.

  • OAuth editOpenidConnect app OAuth openidConnectData

    Note: Choice the Authorization Endpoint according to the identity source you configure.

  • When you want to use you want to use miniOrange as OAuth identity server use this endpoint: https://{mycompany.domainname.com}/moas/idp/openidsso

  • If you are configuring any Identity Provider in Identity Providers Menu and not using miniOrange as IDP use this endpoint: https://{mycompany.domainname.com}/broker/login/oauth{customerid}
  • Select External/JWT App.
  • External JWT app
  • Configure the name for your application and configure Redirect-URL which tells where to send JWT response. Redirect-URL should be an endpoint on your application where you want to achieve SSO.
  • JWT app configure

    In case you are setting up SSO with Mobile Applications where you can't create an endpoint for Redirect or Callback URL, use below URL.

    https://login.xecurify.com/moas/jwt/mobile
  • Click Save
  • To get the SSO link for your application, Go to Apps >> your_app >> select >> Edit.
  • JWT app SSO
  • Then, copy the Single Sign On Url and verify SSO setup by browsing that url.
  • JWT app SSO
  • On successful authentication, you will be redirected to configured Redirect or Callback URL with JWT token
  • You will need to download a certificate from App > Manage Apps, and click Certificate link against your configured application. This certificate will be used for signature validation of JWT response.
  • JWT app SSO certificate

Step 5: Setup Multiple IDPs (Optional)

    You also have a choice to set multiple IDPS for Single Application. And there are two ways to represent them :

  • Login using IDP selection page: gives user an option to Select IDP from dropdown list during login time.
  • Domain Mapping: Here we map the email domains to particular IDP. So when the user enters the Email address with specific domain he would be redirected to Respective IDP.
  • App Identity Provider Mapping: gives user an option to Select one specific IDP for their application before login.
  • Note :At once you can select either of them.

A] Login using IDP selection page

  • You can configure multiple IDPs (identity providers) and give users the option to select the IDP of their choice to authenticate with.
    For Example - It could be multiple AD domains belonging to different departments or multiple okta organizations.
  • Few usecases where customers configure multiple IDPs -

  • Suppose you have a product which many of your clients use and each client has their own unique IDP so you want them to SSO into your product as well using their existing IDP only. miniOrange provides a centralized way to connect with all IDPs in a very easy manner and integrate SSO into your application.
  • Suppose you are providing a course to many universities, each having a unique IDP like Shibboleth, ADFS, CAS, etc. You can provide single sign-on (SSO) into your course application to all these universities by integrating with all of them using a single platform provided by miniOrange.
  • This is the endpoint to call from your saml application -
    For Cloud IDP - https://login.xecurify.com/moas/discovery?customerId=<customer_id>
    For On-Premise IDP - https://yourdomain.com/discovery?customerId=<customer_id>
  • You can see the screenshot below of the IDP Selection Page with a list of IDPs .

    Note: To view the IDP in drop-down list ,go to Identity Providers tab > against your configured IDP > Select >Edit , here Enable the Show IdP to Users option.

    idp selection

  • You can also change the look and feel of this page. Login to miniOrange Admin console. Navigate to Customization -> Branding Configuration. See the below screenshot for reference-
    customize idp selection
  1. You can customize the title of this page.
  2. You can change the logo and favicon for this page.
  3.  You can change the background and button color for this page from admin UI.

B] Login via Domain Mapping

If you have multiple IDPs and you want a certain set of users to authenticate from one IdP whereas another set of users to authenticate from another IdP, based on their email domains then you can achieve this by using the following steps:- Our domain mapping feature

  • We have provided a Domain Mapping field under each IdP where admins can enter the domain eg. demo.com , example.com as shown in the screenshot below.
  • For your reference , Azure AD and Okta is being used as two different IDPs and WordPress is being used as SP. Follow the guides to set up Okta and WordPress at your end.


  • Once the setup is complete you can login through your Wordpress site.
  • Lets Say in Azure AD IDP Domain field we enter example.com and in Okta IDP Domain field we enter demo.com
  • So a user logging in with the example.com domain will be redirected to Azure AD IDP.
  • User logging in with email address having demo.com domain will be redirected to Okta IDP.
  • Once the user will authenticate itself through respective IDPs, it will be redirected back to Wordpress site.

C] Login via App Identity Provider Mapping

    If you have multiple IDPs (identity provider) and you want a certain application user to authenticate with one IDP and other application users with another IDP then you can achieve this by our Identity Source Feature.

  • Go to apps >> your_app >> select >>edit.

  • edit saml app
  • Here You will have an option called as Identity source.

  • The dropdown list would show the list of configured IDPs (Identity providers) in miniOrange Identity Providers tab and Userstore.

  • Select one IDP you want for this application. Click on Save.

  • saml app identity source option
  • Now the users of this application would be able to authenticate only by the IDP(Identity Provider) selected from Identity Source dropdown list.