...
Download the Shibboleth Test Metadata and place it in your shibboleth home directory (/etc/shibboleth or C:\opt\shibboleth-sp\etc\shibboleth).
...
Update the entityID configuration in your shibboleth2.xml
In your shibboleth2.xml, which is located in your shibboleth home directory there should be a section that looks similar to the below.
| Code Block |
|---|
<SSO entityID="urn:mace:incommon:uci.edu">
SAML2
</SSO>
|
If the value of entityID is not "urn:mace:incommon:uci.edu" please go ahead and update that value.
Update the metadata configuration in your shibboleth2.xml.
In your shibboleth2.xml, which is located in your shibboleth home directory there should be a section that looks similar to the below.
...
| Code Block |
|---|
<MetadataProvider type="XML" validate="true" path="metadata.xml"/> |
h2.
Restart Shibboleth
Restart your Shibboleth process
...
Please note that these steps are generic as all Cloud/SaaS solution configurations are slightly different.
Update your entityID
If the value of entityID is not "urn:mace:incommon:uci.edu" please go ahead and update that value.
Update your Shibboleth Metadata
Download the Shibboleth Test Metadata and replace the existing metadata file in your Cloud/SaaS SAML configuration.
Update your endpoints
If your Cloud/SaaS SAML configuration has references to https://shib.service.uci.edu/idp/profile/SAML2/POST/SSO or https://shib.service.uci.edu/idp/profile/SAML2/Redirect/SSO, please replace them with https://shib-staging.service.uci.edu/idp/profile/SAML2/POST/SSO or https://shib-staging.service.uci.edu/idp/profile/SAML2/Redirect/SSO
Test your application
Navigate to your test application and attempt to login. You should be at https://login2.uci.edu.