Guide for shibboleth3 as IdP with Joomla

Download Module

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

Step 1: Setup Shibboleth3 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="InlineMetadataProvider" 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 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 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 Service Provider.

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 2: Configuring Joomla as Service Provider (SP)

In miniOrange SAML plugin, go to Service Provider Setup Tab. There are two ways to configure the plugin with your IDP(Shibboleth3-idp):

I. By Uploading Shibboleth3 Metadata.xml file(Recommended):

II. Manual Configuration :

In miniOrange SAML plugin, go to Service Provider Setup Tab. Enter the following values:

IDP Entity ID	Identity Provider Issuer from Shibboleth3 Setup Instructions
Single Sign-On Service URL	Identity Provider Single Sign-On URL from Shibboleth3-idp Setup Instructions
X.509 Certificate	X.509 Certifiacate from Shibboleth3 Setup Instructions

III. Add a button on your site login page with the following URL:

Step 3: Attribute Mapping (It is Optional to fill this). This is Premium feature.

Attributes are user details that are stored in your Identity Provider.
Attribute Mapping helps you to get user attributes from your Identity Provider (Shibboleth3-idp) and map them to Joomla user attributes like firstname, lastname etc.
While auto registering the users in your Joomla site these attributes will automatically get mapped to your Joomla user details.

In miniOrange SAML plugin, go to Attribute Mapping tab and fill in all the fields.

Username:	Name of the username attribute from IdP (Keep NameID by default)
Email:	Name of the email attribute from IdP (Keep NameID by default)
Group/Role:	Name of the Role attribute from your Identity Provider (Shibboleth3-idp)

You can check the Test Configuration Results under Service Provider Setup tab to get a better idea of which values to map here.

Step 4: Group Mapping (It is Optional to fill this). This is Premium feature.

Joomla uses a concept of Roles, designed to give the site owner the ability to control what users can and cannot do within the site.
Role mapping helps you to assign specific roles to users of a certain group in your Identity Provider (Shibboleth3-idp).
While auto registering, the users are assigned roles based on the group they are mapped to.

Step 5: Redirection & SSO Links.

Go to Redirection & SSO Links tab. There are multiple features availabe in this tab like Auto redirect the user to Identity Provider and Enable Backed Login for Super Users.To use these features, click on the respective checkboxes.

You have successfully Installed and Configured plugin

Business Trial For Free

If you don't find what you are looking for, please contact us at joomlasupport@xecurify.com or call us at +1 978 658 9387.

Guide for shibboleth3 as IdP with Joomla

Step 1: Setup Shibboleth3 as Identity Provider

Step 2: Configuring Joomla as Service Provider (SP)

Step 3: Attribute Mapping (It is Optional to fill this). This is Premium feature.

Step 4: Group Mapping (It is Optional to fill this). This is Premium feature.

Step 5: Redirection & SSO Links.

You have successfully Installed and Configured plugin

Additional Resources

Contents

STAY CONNECTED

Product

Solutions

Why miniorange

Company