> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Keystore Management
> You can define and manage keystores used in policies. You can perform keystore addition, deletion, and update operations with JKS, PKCS12, and PEM format support. These operations can only be performed by Admin users.
## Creating a New Key Store
Click the **Create** button from the **Management → Secrets Management → Key Stores** screen. Fill in the information under **Definition**. Then click the **New Key Store Definition** button.
The fields used for Key Store creation configuration:
| Field | Description |
| ----------- | --------------------------------------------------------------------------------------- |
| Name | Name information of the created Key store. |
| Description | A description can be written to facilitate management related to the created Key Store. |
Fill in the configuration information for the Key Store in the opened window. Then click the **Save** button. The saved **Key Store Definition** is listed in the table opened under **Configuration**.
The fields used for Key Store definition configuration:
| Field | Description |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Environments (Environments) | The previously defined environment where the Key Store will be used is selected. |
| Key Store Type (Key Store Type) | The type of the Key Store is selected. Three options are available:
• JKS
• PKCS12
• PEM |
| File (File) | The file containing the Key Store is selected by clicking the "Select File" button.
• Allowed formats: .jks, .pkcs12, .p12, .pfx, .pem, .crt, .cer |
| Alias | The alias information of the Key Store is entered. |
| Password (Password) | This is the field where the password for the Key Store is entered. |
After completing the definition and configuration information, click the **Save and Deploy** button to deploy.
## Key Store Editing
To edit an existing Key Store, click the **Edit** button from that Key Store's menu.
To edit the configuration information belonging to the Key Store, click the **Edit** button from the menu under the configuration list.
After clicking the "Edit" button to edit the Key Store, the steps followed during creation are followed.
### Updating Related JWKs
When a Key Store is updated and the **Save and Deploy** button is clicked, if there are JWKs created from this keystore, the system automatically detects related JWKs and presents the user with options.
When a Key Store is updated, JWKs created from this keystore can also be automatically updated or the relationship can be disconnected.
#### JWK Connection Dialog
When a Key Store is updated and related JWKs are detected, the following dialog opens:
**Dialog Content:**
* **Title**: "JWK Connection"
* **Warning Message**: "This Key Store is used in X JWK(s). What would you like to do?"
* **Options**:
* **Update related JWKs**: Ensures that changes in the Key Store are reflected to related JWKs as well.
* **Update keystore only and disconnect**: Updates the Key Store but disconnects the relationship with JWKs.
* **Cancel**: Cancels the operation.
#### Update Flow
Edit the Key Store information and click the **Save and Deploy** button.
The system checks for JWKs created from this keystore.
If there are related JWKs, the JWK Connection dialog opens.
The user selects one of three options: Update, Disconnect, or Cancel.
When Update or Disconnect is selected, a confirmation dialog opens. The user confirms the operation by entering the keystore name.
After confirmation, the selected operation is performed and the keystore is updated.
Updating related JWKs may affect all policies and connections using these JWKs. Evaluate the impacts before proceeding.
## Key Store Deletion
To delete an existing Key Store, click the **Delete** button from that Key Store's menu.
Click the **Delete** button again in the opened window to confirm.
