#Axway secure transport default password password

Key Size вЂ“ a number representing the size of the generated key, expressed in bits.

#Axway secure transport default password password

Confirm CA key password вЂ“ the key password must be entered again for confirmation.This password is requested when generating certificate signed by the internal CA. CA key password вЂ“ the password to protect internal CA.Validity in days вЂ“ the number of days the certificate is valid.For internal certificates, provide following information: Internal certificates require the Certificate Subject information.Provide the required information for the internal certificate.The Generate Internal CA dialog box is displayed.The most common reason is that the current CA is nearing its expiration date. There are a number of reasons why you might want to generate an internal CA. Basic certificate information is displayed including the validation status.The following topics provide how-to instructions for managing the internal CA: This has critical impact on the generated Login Certificates because users are no longer able to log into the SecureTransport Server. If the certificate of the internal CA is deleted the Validation Status of all X509 local certificates, as well as imported SSH keys (because they are converted to X509 certificates during the import,) become Not chained to a trusted root. If you attempt to delete the internal CA, an alert dialog box is displayed. In addition to issuing certificates signed by internal CA, SecureTransport supports a few management operations for the internal CA. For contact information, see Get more help on page 1. Contact Axway Global Support for more information.

This password cannot be retrieved if it is lost. Any operation that involves use of the internal CA require that password. The internal CA key is protected with a password. For detail, see Import an SSH login public key. For detail, see Manage local certificates and certificate signing requests. It is used implicitly in the following cases: It provides a convenient alternative to using a third-party CA. The internal CA can be used to generate server or client certificates. If you have a disaster recovery site, the DR cluster should use the same internal CA, replicated from the primary production site.ДЇor security reasons, client certificates should only be stored inside the SecureTransport home folder or within a sub-folder of the home folder. All SecureTransport Servers in a cluster share the same internal CA. During the initial post-installation setup procedure, an internal CA is generated. Each SecureTransport installation maintains its own copy of the internal CA.