Security Configuration
You configure the security services in the Integration Directory to ensure secure communication with your trading partners when using the RNIF Adapter.
You have created a new Sender or Receiver Agreement and chosen the appropriate communication channel.
You configure the following values
Field |
Value |
Trust Model |
Direct or Hierarchical. If the Direct Trust Model is used, the validation of the partner certificate is realized as a direct comparison against the certificate in the J2EE key store. If the Hierarchical model is used, the adapter checks for the trust worthiness of the certificate and verifies it against the issuer’s certificate (CA certificate) by looking through the certificate chain in the certificate. |
Encryption Policy |
You can choose from three levels: · None · Payload · Payload Container In case of Payload encryption, the service content as well as the optional message attachments are encrypted. In case of Payload Container encryption, the service header and the service content together with the optional message attachments are encrypted. You must also choose the corresponding algorithm here. The available options are RC2-40, RC2-128, and 3DES. RC2-40 specifies a keysize of 40 while RC2-128 specifies a keysize of 128. RC2-40 is a weak algorithm. For a more secure encryption, use RC2-128 or 3DES. |
Current Certificate for Decryption |
Enter values for the Keystore View name and Keystore Entry here. The Keystore is available in the SAP J2EE Engine and within this you can add a view and corresponding keys and certificates. Enter the Keystore view name corresponding to the view that you created in the SAP J2EE Engine Keystore. The Keystore Entry must have the name of your private key. |
Partner Certificate for Encryption |
Enter values for the Keystore View name and Keystore Entry here. The Keystore Entry of the partner must correspond to the encryption certificate name of the partner. In case of the Hierarchical Trust Model, also enter the Certification Authority Keystore view name, which contains the Certification Authority’s certificates. |
Current Certificate for Signing |
Choose the algorithm SHA1 from the dropdown box. Only this algorithm is supported. The Keystore Entry must have the name of your private key. |
Partner Certificate for Signing |
In case of Direct Trust model, enter values for the Keystore View name and Keystore Entry here. The Keystore Entry of the partner must correspond to the signing certificate name of the partner. In case of the Hierarchical Trust Model, enter values of subject name and the issuer name of the signing certificate name of the partner. Also enter the Certification Authority Keystore view name, which contains the reference to the certificate of the Certification Authority. |