Use this process if you have a Shibboleth SP and the standard metadata endpoint (https://<your dns name>/Shibboleth.sso/Metadata) is accessible (i.e. not on a private network or firewalled from the SP Registry):
- Click "Register a New Service Provider"
- Enter your SP's entityID
- Click "Continue"
- In the window that opens, select choice #1. Most of your metadata will be filled in automatically on the registration form. If you did not meet the ownership requirements in step 1 of the "Registration overview" you will receive the error "No permission for <entityID>".
- Enter your organization information (Name, Display name, and URL)
- Enter the name, email address, and phone number for at least one contact (two contacts are strongly recommended)
- Verify that the other metadata is correct for your installation, meaning it matches what you have configured in your shibboleth2.xml file.
- Click "Save changes"
Allow a few minutes for your SP information to propagate to the UW IdP. Testing won't work until this completes. See
Flow of Metadata and Filter Policies from SP Registry to the IdP.
- Click "Register a New Service Provider"
- Enter your SP's entityID
- Click "Continue"
- In the window that opens, select choice #2. Enter a URL accessible to the SP Registry where you have placed your SP metadata file. Most of your metadata will be filled in automatically on the registration form. If you did not meet the ownership requirements in step 1 of the "Registration overview" you will receive the error "No permission for <entityID>". If a valid metadata file was not found at that URL, you will receive the error "URL did not respond with metadata".
- Enter your organization information (Name, Display name, and URL)
- Enter the name, email address, and phone number for at least one contact (two contacts are strongly recommended)
- Verify that the other metadata is correct for your installation, meaning it matches what you have configured in your shibboleth2.xml file.
- Click "Save changes"
Allow a few minutes for your SP information to propagate to the UW IdP. Testing won't work until this completes. See
Flow of Metadata and Filter Policies from SP Registry to the IdP.
- Click "Register a New Service Provider"
- Enter your SP's entityID
- Click "Continue"
- In the window that opens, select choice #3. A registration form will be displayed. If you did not meet the ownership requirements in step 1 of the "Registration overview" you will receive the error "No permission for <entityID>".
- Enter your organization information (Name, Display name, and URL)
- Enter the name, email address, and phone number for at least one contact (two contacts are strongly recommended)
- Check the boxes for protocols your SP will support
- In the KeyInfo section, update the certificate name as appropriate and paste in the text of your SP's PEM formatted certificate
- In the ACS (Assertion Consumer Service) section, verify that the binding and location information is correct for each ACS. The values provided in the form are only educated guesses based on default Shibboleth configurations and the entityID you provided. It is your responsibility to ensure the information matches what you have configured in your shibboleth2.xml file
- If you need to add an additional ACS, click "Add ACS," select the binding from the drop-down menu, and enter the correct URL for the location
- If you want to delete an ACS, click the "X" next to the location text box
- Click "Save changes"
Allow a few minutes for your SP information to propagate to the UW IdP. Testing won't work until this completes. See
Flow of Metadata and Filter Policies from SP Registry to the IdP.
You can register your SP, or update it, by
PUTing your metadata document to the SP Registry's metadata endpoint.
- PUT https://iam-tools.u.washington.edu/spreg/ws/metadata?id={your_SP's_entity_id}&mdid=UW
- Authenticate with a UWCA certificate
- The CN or an alt_name must match the host name, or a sub-domain, of the DNS portion of the entity id.
- The CN or an alt_name must match the host name, or a sub-domain, of the DNS portion of the entity id.
- The content is your metadata document.