| 16 | | 1. Open the shibboleth2.xml file in the etc directory of the Shibboleth SP installation and edit the ISAP tag, RequestMap tag, ApplicationDefaults tag, SSO tag, and MetadataProvider tag as follows and save the file. The site id comes from the value in the IIS control panel associated with the web site that is configure to work with the Shibboleth SP. The name and hostname should be the outwardly listening IIS interface that the web browser will be connecting to. The entityID in the ApplicationDefaults tag should looks something like: https://thefullhostname/shibboleth . The entityID in the SSO tag should be the entityID copied from the idp-metadata.xml file. The file name in the MetadataProvider should point to the idp-metadata.xml file saved in the etc directory of the Shibboleth SP installation. It should not include any directory components, just the filename. |
| | 16 | 1. Open the shibboleth2.xml file in the etc directory of the Shibboleth SP installation and edit the ISAP tag, !RequestMap tag, !ApplicationDefaults tag, SSO tag, and !MetadataProvider tag as follows and save the file. The site id comes from the value in the IIS control panel associated with the web site that is configure to work with the Shibboleth SP. The name and hostname should be the outwardly listening IIS interface that the web browser will be connecting to. The entityID in the !ApplicationDefaults tag should looks something like: https://thefullhostname/shibboleth . This should _not_ be the URL for the web server. The entityID in the SSO tag should be the entityID copied from the idp-metadata.xml file. The file name in the !MetadataProvider should point to the idp-metadata.xml file saved in the etc directory of the Shibboleth SP installation. It should not include any directory components, just the filename. |
