Represents a collection of X.509 certificates that are provided to authenticate security credentials issued from a Security Token Service (STS).
<knownCertificates> <add findValue="String" storeLocation="CurrentUser/LocalMachine" storeName=" CurrentUser/LocalMachine" x509FindType="FindByThumbprint/FindBySubjectName/FindBySubjectDistinguishedName/FindByIssuerName/FindByIssuerDistinguishedName/FindBySerialNumber/FindByTimeValid/FindByTimeNotYetValid/FindBySerialNumber/FindByTimeExpired/FindByTemplateName/FindByApplicationPolicy/FindByCertificatePolicy/FindByExtension/FindByKeyUsage/FindBySubjectKeyIdentifier" /> </knownCertificates>
Attributes and Elements
The following sections describe attributes, child elements, and parent elements
|<add>||Adds an X.509 certificate to the collection.|
|<issuedTokenAuthentication>||Specifies a token issued as a service credential.|
The issued token scenario has three stages. In the first stage, a client trying to access a service is referred to a secure token service. The secure token service then authenticates the client and subsequently issues the client a token, typically a Security Assertions Markup Language (SAML) token. The client then returns to the service with the token. The service examines the token for data that allows the service to authenticate the token and therefore the client. To authenticate the token, the certificate the secure token service uses must be known to the service.
The <issuedTokenAuthentication> element is the repository for any such secure token service certificates. To add certificates, use the <knownCertificates> element. Insert an <add> for each certificate, as shown in the following example.
<issuedTokenAuthentication> <knownCertificates> <add findValue="www.contoso.com" storeLocation="LocalMachine" storeName="My" X509FindType="FindBySubjectName" /> </knownCertificates> </issuedTokenAuthentication>
By default, the certificates must be obtained from a secure token service. These "known" certificates ensure that only legitimate clients can access a service.
To review conditions required for a client to be authenticated by a federated service, as well as more information on using this configuration element, see How to: Configure Credentials on a Federation Service. For more information about federated scenarios, see Federation and Issued Tokens.
For an example that shows how to populate the collection in configuration, see <add>.
- Security Behaviors
- How to: Configure Credentials on a Federation Service
- Working with Certificates
- Federation and Issued Tokens
- Securing Services and Clients