Configuring a SAML Token Processor instance
The integrated SAML (1.1 or 2.0) Token Processor accepts and validates SAML (1.1 or 2.0) security tokens. The PingFederate security token service (STS) validates digital signatures using all trusted certificate authorities (CAs) imported into PingFederate.
|
The |
About this task
On the Instance Configuration tab, configure a SAML Token Processor instance.
You can restrict the signature verification process by subject distinguished names (DN), issuers, or both to limit the token requests accepted for this token processor instance.
You must indicate a unique identifier for the PingFederate STS. Token processor instances reject SAML tokens that do not contain the identifier in the audience element.
Steps
-
Go to Authentication > Token Exchange > Token Processors.
-
On the Instance Configuration tab, configure the basics of the token processor instance.
-
In the field value field of the Audience row, enter the URI that uniquely identifies your federation gateway for this SAML protocol.
This is the federation ID for the STS for either SAML 1.1 or SAML 2.0 tokens, depending on which processor you are configuring.
-
(Optional) Click Add a new row to 'Valid Certificate Issuer DNs' to enter one or more issuers.
If issuer DNs are specified here, then only those issuers are considered valid for verifying incoming digital signatures. Otherwise, all trusted certificate authorities (CAs) are used to verify signatures.
-
(Optional) Click Add a new row to 'Valid Certificate Subject DNs' to enter one or more subject DNs.
If subject DNs are specified here, then only those subject DNs are considered valid for verifying incoming digital signatures. Otherwise, all trusted certificate authorities (CAs) are used to verify signatures.
If you specify both issuer DNs and subject DNs, then the certificate used to validate signatures must match an entry in both lists.
If you provide no issuer DN and subject DN, then all certificates are treated as valid for purposes of verification.
-