Save and close the attribute-filter.xml file. Restarting Shibboleth 2 IdP and verifying functionality To restart Shibboleth 2 IdP and verify functionality, proceed with the following steps: Follow the steps as per section § Restarting the Shibboleth web server to take into account the updated configuration. Follow the steps as per section § Ensuring that the Shibboleth IdP is running. Follow the steps as per section § Performing configuration tests. These steps stop and start Apache Tomcat to restart Shibboleth 2 IdP and ensure the updated XML files are loaded. Shibboleth may fail to start if there is a problem with one or more of the configuration files. In the Shibboleth 2 IdP status page, Azure AD should normally appear as a Relying Party at the bottom: If you encounter any issue, check Tomcat and Shibboleth’s log files after restart, located at: %TOMCAT_HOME%\logs\ catalina.DATE.log localhost.DATE.log %IDP_HOME%\logs\ idp-process.log If you are still stumped, please check out on the Shibboleth Community wiki. Installing Windows PowerShell for single sign-on with Shibboleth 2 Azure AD domains are federated using Windows PowerShell and cmdlets of the Microsoft Online Services Module for Windows PowerShell. Note For additional information, see the Microsoft TechNet article .
Save and close the attribute-filter.xml file. Restarting Shibboleth 2 IdP and verifying functionality To restart Shibboleth 2 IdP and verify functionality, proceed with the following steps: Follow the steps as per section § Restarting the Shibboleth web server to take into account the updated configuration. Follow the steps as per section § Ensuring that the Shibboleth IdP is running. Follow the steps as per section § Performing configuration tests. These steps stop and start Apache Tomcat to restart Shibboleth 2 IdP and ensure the updated XML files are loaded. Shibboleth may fail to start if there is a problem with one or more of the configuration files. In the Shibboleth 2 IdP status page, Azure AD should normally appear as a Relying Party at the bottom: If you encounter any issue, check Tomcat and Shibboleth’s log files after restart, located at: %TOMCAT_HOME%\logs\ catalina.DATE.log localhost.DATE.log %IDP_HOME%\logs\ idp-process.log If you are still stumped, please check out on the Shibboleth Community wiki. Installing Windows PowerShell for single sign-on with Shibboleth 2 Azure AD domains are federated using Windows PowerShell and cmdlets of the Microsoft Online Services Module for Windows PowerShell. Note For additional information, see the Microsoft TechNet article .
AAD-Office-365-Single-Sign-On-with-Shibboleth-2.docx