If you have an existing server. keystore in this directory, you first need to delete the existing key pair using that alias.

（如果在此目录中已经有一个server.keystore，那么首先需要删除使用该别名的现有密匙对）。

alias is the alias to use for the keystore entry that stores the generated private key and certificate.

alias是用于keystore项的别名，keystore存储生成的私有密钥和证书。

The Available flag indicates whether that password has been saved in order to make the keystore available to other components in the server.

Available标志指示是否保存了密码，使密钥存储库用于服务器中的其他组件。

The conssl. cfg file is only used by SQLI clients, and contains the location of client keystore and client stash file.

cfg文件仅供SQLI客户机使用，并且包含客户机密钥库和客户机存储文件的位置。

Missing values for keystore and stash file location in conssl. cfg file

cfg文件中缺少密钥库的值和存储文件位置

Community Edition creates a new keystore with name "ca-keystore, " and generates a new keypair and a self-signed certificate.

CommunityEdition将创建一个名为“ca-keystore”的新密钥存储库，并生成一个新密钥对和一个自签名证书。

The Editable and Available columns show whether the keystore is locked or unlocked for editing and availability, respectively.

Editable和Available列显示该密钥存储库是被锁定还是未被锁定（分别对应于编辑和可用性）。

The Java Runtime Environment (JRE) provides a default keystore for CA certificates, called cacerts, which you will use here.

Java运行时环境（JavaRuntimeEnvironment，JRE）为CA证书提供一个缺省密钥库，即cacerts，您可以在此处使用它。

demo. kdb is the name of the key database (or keystore ) in which the certificate request is to be created

kdb是创建证书请求的密钥数据库（或密钥库）的名称

Keystore Password: Password used to access the keystore file and the private-key entry.

KeystorePassword：用于访问密钥存储库文件和私钥项的密码。

SSL_KEYSTORE _STH is the fully qualified file name of the stash file containing the encrypted keystore password.

SSL_KEYSTORE_STH是包含加密密钥库密钥的存储文件的完全限定名。

Overview of SSL keystore and truststore setup

SSL密钥存储区和信任存储区设置概述

The referenced keystore file must be present in the classpath at run time.

被引用的keystore文件必须在运行时提供给类路径。

’ and browse to save in the same place as the saved keystore file, accept the name of cert. arm and the given type.

并将其保存到与保存的密钥库文件相同的地方，接受cert.arm的名称和指定的类型。

As well as the InputStream, the KeyStore needs to know the format of the stream (we use the default, "jks" ) and the store password.

除了InputStream，KeyStore需要知道流的格式（我们使用缺省的“jks”）和存储密码。

Creating and configuring the client-side keystore (optional)

创建并配置客户端密匙存储（可选）

Create server keystore .

创建服务器密钥库。

Create client keystore .

创建客户机密钥库。

Creating a keystore .

创建一个密钥库。

This initial configuration uses a keystore you can use for testing, but you should not use it in a production environment.

此初始配置使用了一个密钥存储，您可以将其用于测试，但不能将其用于生产环境。

Once you receive the reply from CA you can import that certificate into the keystore .

从CA收到应答后，您可以将该证书导入到密钥存储库。

Certificates stored in the keystore are protected with a password, which must be provided to the jarsigner tool to sign a JAR file.

存储在keystore中的证书有密码保护，必须向jarsigner工具提供这个密码才能对JAR文件签名。

The default keystore in Community Edition with a certificate provided is "geronimo-default. "

带有证书的CommunityEdition中的缺省密钥存储库是“geronimo-default”。

Click a "locked" icon (shown in the Editable column) and provide the password used at keystore creation time to unlock a keystore.

单击锁定图标（显示在Editable列中），并提供在创建密钥存储库时使用的密码来取消锁定该密钥存储库。

For Confirm password, enter the keystore password.

对于Confirmpassword，输入密钥存储密码。

In the case of SSH, two different processes do this, hence loading of the keystore fails.

对于SSH，两个不同的进程执行这个过程，因此无法装载密钥存储。

For the EFS keystore to load, creation of the keystore and binding of these keys to process credentials has to be done by a single process.

对于要装载的EFS密钥存储，必须由单一进程创建密钥存储并把这些密钥与进程凭证绑定。

For the final step, export the client certificate and import that into the server keystore , by first running (entered as a single line)

对于最后一步，导出客户机证书并将其导入到服务器serverkeystore，输入以下命令（以单行形式输入）

Relax JSSE’s restriction that KeyStore passwords and individual certificate passwords must match

放宽KeyStore密码与单个证书密码必须匹配的JSSE限制

The location and name of the server keystore and server stash file is predefined

服务器密钥库和服务器存储文件的位置和名称是预定义的