...
Metadata Elements
Entity ID
https://spaces.at.internet2.edu/display/InCCollaborate/Entity+IDs
The first step is to choose an entity ID for each of the SAML entities to be deployed. Please choose these names with care, because once you publish them, it will be difficult to change the names later on.
Scope
TBD
User Interface Elements
...
https://spaces.at.internet2.edu/display/InCCollaborate/RequestedAttributes
X.509 Certificates
A SAML entity uses public key cryptography to secure the data transmitted to trusted partners. Public keys are published in the form of X.509 Certificates in Metadata. The corresponding private keys are held securely by the SAML entity. These keys are used for message-level signing and encryption, and to create secure channels for transporting SAML messages.
| Info | ||
|---|---|---|
| ||
X.509 certificates in metadata are used for SSL/TLS back-channel SOAP exchanges, typically on a port like 8443. These certificates are not the same as and have nothing to do with SSL/TLS certificates used for browser-facing transactions over port 443. The latter certificates are not contained in metadata. |
Any certificates you want to use with your SAML software are uploaded via the administrative interface. You can upload multiple certificates for different purposes or to facilitate the controlled rollover of expired certificates. For detailed guidelines on the rollover process, refer to the Certificate Migration topic.https://spaces.at.internet2.edu/display/InCCollaborate/X.509+Certificates+in+Metadata
Discovery
(refer to the User Interface Elements for IdPs)
...