For browser-based single sign-on (SSO), if you choose to encrypt all or part of an SSO assertion on, you must identify the certificate that PingFederate can use to do so.
You must also select a certificate if your requirements include encrypting an assertion in response to an attribute query on.
For WS-Trust security token service (STS), this configuration is also required if you enabled the Generate Key for SAML Holder of Key Subject Confirmation Method or Encrypt SAML 2.0 Assertion option, or both, on .
If encryption is not required, the Select XML Encryption Certificate tab is not shown.
Select an option under Block Encryption Algorithm.
Due to the import restrictions of some countries, Oracle Server Java SE Runtime Environment (JRE) 8 has built-in restrictions on available cryptographic strength (key size). To use larger key sizes, enable the Java Cryptography Extension (JCE) unlimited strength jurisdiction policy. For more information, see the Java 8 release notes in Oracle's documentation.
For Oracle Java SE Development Kit 11, the JCE jurisdiction policy defaults to unlimited strength. For more information, see the Oracle JDK Migration Guide in Oracle's documentation.
The default selection is AES-128.
For more information about XML block encryption and key transport algorithms, see XML Encryption Syntax and Processing from W3C.
Select an option under Key Transport Algorithm.
Due to security risks associated with the RSA-v1.5 algorithm used for key transport, it is no longer available for new connections. Existing connections in which this algorithm is configured continue to support it. However, you should upgrade such connections to use the newer algorithm RSA-OAEP.
The default selection is RSA-OAEP.
Select a partner certificate from the list.
If you have not imported the certificate from your partner, click Manage Certificates to do so. For more information see Managing certificates from partners.