Create a Self-Signed Certificate
You can create a self-signed certificate from the Administration menu.
Check in the public part of the self-signed certificate into the Trusted store of Sterling B2B Integrator. To create a self-signed certificate:
- Choose one of the following options:
- If you use Sterling B2B Integrator, from the Administration Menu, select .
- If you use the AS2 Edition, from the AS2 Administration menu, select Certificates.
- Next to Create Self-signed Certificate, click Go!
- Enter the Name of the self-signed certificate.
- Enter the name of the Organization.
- Select the Country or origin of the self-signed certificate.
- Enter a contact e-mail address for the person responsible for certificates in the organization and then click Next.
- Enter the Serial Number for the
certificate. The serial number is the number you want to assign to the self-signed certificate.
- Enter the Duration (number of days) that the self-signed certificate is valid.
- Enter the IP addresses of the network interfaces you want to associate with the certificate as the SubjectAltName field.
- Enter the DNS Names of the network interfaces you want to associate with the certificate as the SubjectAltName field.
- Select the Key Length. Select one
of the following key lengths:
Note: The key length 1024 provides a good balance between security, interoperability, and efficiency. The key length 2048 is the most secure, but also the slowest, and may not work with some applications. For information about defining EBICS-specific key lengths for electronic signature, encryption, and authentication, see EBICS Specification, version 2.5.Note: If you select the key length 512, you must check for JDK restrictions on the key length in the java.security file in the JDK. Else, protocol communication might fail during run time.
- Select the Signing Algorithm.
Note: You must use the SHA256withRSA signing algorithm for certificates used with EBICS transactions.
- Select the Validate When Used option.
Validation options are:
- Validity – Verifies dates in the validity period of the certificate
are still in effect. If the dates are not in effect, the certificate
is not used. Note: Before you set a value to the validity period of the certificate, you must read and apply the best practice recommendations from the Microsoft PKI Quick Guide. For information about the best practice recommendations for using certificates, see http://www.windowsecurity.com/articles/Microsoft-PKI-Quick-Guide-Part3.html.
- Auth Chain – Constructs a chain of trust for certificates that are not self-signed. If a chain of trust cannot be constructed using valid certificates, the certificate is not used. If the certificate is self-signed, this option verifies only the certificate signature.
- Validity – Verifies dates in the validity period of the certificate are still in effect. If the dates are not in effect, the certificate is not used.
- Set the Certificate Signing Bit by selecting the check box.
- Click Next.
- Review the information about the self-signed certificate.
- Click Finish.