Deploy Shibboleth Identity Provider cluster on Windows

Azure Public Test Date Azure Public Test Result

Azure US Gov Last Test Date Azure US Gov Last Test Result

Bicep Version

Best Practice Check Cred Scan Check

Deploy To Azure Deploy To Azure US Gov Visualize

This template deploys Shibboleth Identity Provider on Windows in a clustered configuration. It creates a one or more Windows VM for the front end and a single VM for the backend. It does a silent install of Apache Tomcat and Open JDK on the front end VM's, and then deploys Shibboleth IDP on each of them. It also deploys MySQL on the backend VM. It configures a load balancer for directing requests to the front end VM's. It also configures NAT rules to allow admin access to each of the VM's. On backend VM's, it configures the database using JPA. After the deployment is successful, you can go to https://your-domain:8443/idp/profile/status (note port number) to check success. Note that, in case of smaller size VM's, it may take a few minutes for the installation script to complete even after the deployment status is shown as succeeded. For further details, please refer to the Shibboleth IDP documentation at

Front End VM's

This template can instantiate up to 5 front end VM's. This number can be increased easily by copying and pasting the related parts of the template.

Port Details

The template opens HTTP port 8443 for SSL front end access on all the front end VM's. This port is load-balanced using the load balancer. It also opens ports 2200 to 2204 on the load balancer which are mapped to port 22 for SSH admin access on the respective VM's.


In order to support SSL, this template creates self signed certificates as a part of the installation script. This allows the template to be deployed without having to create your own certificates. In production deployments, you will need to create and use your own certificates instead of the self signed certificates.

Test Setup

Here are the steps you can follow to create a testing setup including Shibboleth IDP deployed using this template, along with an OpenLDAP test server and a test SP available online.

Deploy Shibboleth IDP using this template

Create a deployment of Shibboleth IDP using this template and RDP into the VM deployed.

Update inside /opt/conf directory as per the LDAP configuration

Following are the settings for Online LDAP Test Server installation hosted at

  • set idp.authn.LDAP.authenticator = bindSearchAuthenticator
  • set idp.authn.LDAP.ldapURL = ldap://
  • set idp.authn.LDAP.useStartTLS = false
  • set idp.authn.LDAP.useSSL = false
  • set idp.authn.LDAP.baseDN = dc=example,dc=com
  • set idp.authn.LDAP.bindDN = cn=read-only-admin,dc=example,dc=com
  • set idp.authn.LDAP.bindDNCredential = password
  • set idp.authn.LDAP.dnFormat = uid=%s,dc=example,dc=com
  • Comment out idp.authn.LDAP.sslConfig & Comment out idp.authn.LDAP.trustCertificates as SSL is not used here

Create metadata xml file for service provider

Note: is used as Service provider and Shibboleth is used as IDP.

<!-- TestShib -->
<MetadataProvider id="HTTPMetadataTESTSHIB"

Set LDAP attribute resolver

  • Set LDAP Attribute Resolver as default attribute resolver. The default configuration for LDAP attribute resolver is present inside attribute-resolver-ldap.xml We just have to replace existing attribute-resolver.xml with attribute-resolver-ldap.xml
  • These files are present in /opt/conf/ directory
  • Following commands rename attribute-resolver-ldap.xml to attribute-resolver.xml
sudo mv attribute-resolver.xml attribute-resolver-orig.xml
sudo cp attribute-resolver-ldap.xml attribute-resolver.xml
sudo vi attribute-resolver.xml

Configure attribute-resolver

  • Configure the mapping of LDAP attributes with Shibboleth attributes
  • These instructions would vary as per LDAP installation. Following are specific to forumsys ldap
  • Set sourceAttributeId attribute of Attribute with id=eduPersonPrincipalName to uid
<resolver:AttributeDefinition id="eduPersonPrincipalName" xsi:type="ad:Prescoped" sourceAttributeID="uid">
    <resolver:Dependency ref="myLDAP" />
    <resolver:AttributeEncoder xsi:type="enc:SAML1ScopedString" name="urn:mace:dir:attribute-def:eduPersonPrincipalName" encodeType="false" />
    <resolver:AttributeEncoder xsi:type="enc:SAML2ScopedString" name="urn:oid:" friendlyName="eduPersonPrincipalName" encodeType="false" />
  • In the bottom of same xml we need to configure data connector settings for LDAP. Again these settings vary as per LDAP setup.
<resolver:DataConnector id="myLDAP" xsi:type="dc:LDAPDirectory"

Configure attribute filter

  • After defining attributes you still have to specify which ones you release to service providers. This can be configured using attribute-filter.xml inside /opt/conf directory
  • We set it so that basic attribute like eduPersonPrincipalName, uid and email are sent to all service providers.
<AttributeFilterPolicy id="example1">
<PolicyRequirementRule xsi:type="ANY" />

Comment out following in to use Shibboleth.StorageService instead of Shibboleth.JPAStorageService

  • idp.consent.StorageService
  • idp.consent.userStorageKey
  • idp.consent.userStorageKeyAttribute

Add following environment variable inside startup.bat of Apache Tomcat

  • set IDP_HOME=c:/opt/shibboleth-idp

Restart the servlet container

  • cd C:\apache-tomcat-7.0.67\bin\
  • Start-Process .\startup.bat

Test your installation

  • Follow the steps on to test the shibboleth installation as IDP
  • Log files for Shibboleth reside inside /opt/logs directory. The log files can be helpful for debugging any issues that show up during the login process.

Tags: Microsoft.Storage/storageAccounts, Microsoft.Compute/availabilitySets, Microsoft.Network/publicIPAddresses, Microsoft.Network/virtualNetworks, Microsoft.Network/networkInterfaces, Microsoft.Network/loadBalancers, Microsoft.Compute/virtualMachines, Microsoft.Network/networkSecurityGroups, Microsoft.Compute/virtualMachines/extensions, CustomScriptExtension