Choosing an encryption certificate (SAML 2.0)
If SAML_SUBJECT is encrypted, either by itself or as part of a whole assertion, then all references to this name identifier in SAML 2.0 single logout (SLO) requests from your site might also be encrypted if the connection uses service provider (SP)-initiated SLO.
About this task
You must also choose a certificate if encryption of the name identifier is required for an Attribute Request profile. For more information, see Specifying XML encryption policy (for SAML 2.0).
Steps
-
Optional: Select an option under Block Encryption Algorithm.
Because of 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 a newer algorithm.
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.