Earlier in the Adeptia Suite, you could not create any separate Truststores. Now you can create separate Keystores and Truststores. A keystore is collection of certificates and private keys. You can use a keystore with your security policies and web service consumer activities. Keystore stores your certificates and private keys that you can give to your client. Whereas, a Truststore stores all your trusted parties' certificates. Adeptia Suite also allows backward compatibility to support all you previously created keystores. However, the Adeptia Suite will treat all of your previous truststores as keystores.
You can create a keystore either manually or by uploading a keystore file. If you want to manually create a keystore then, you need to provide information for many fields. You can find the description about these fields in the table below.
Table 1: Description of Keystore Fields
Keystore Fields | Description |
---|---|
KeyStore Password | Enter a password of your keystore that you want to set |
Confirm Password | Confirm the password of your keystore |
Private Key Password | Enter a password of your private key that you want to set |
Confirm Password | Confirm the password of your private key |
Alias | Enter a name for the identity of the keystore that you are creating |
Key Algorithm | Select an algorithm to encrypt your keystore. You can choose from either DSA or RSA |
Key Size | Specify the encryption key size of the encryption algorithm. The minimum size for DSA is 512 and for RSA is 1024 but we recommend you to use an algorithm of at least 1024 and 2048 key size respectively. |
Common Name | Enter a name that you want to associate with the generated certificate, like a name of a person, e.g. "Susan Jones". |
Organization Unit | Name of the organization unit where you work |
Organization Name | Name of your organization |
Locality | Locality of your organization |
State | State where your organization is situated |
Country | Country where your organization is located |
Validity | Enter the number of days for which your keystore will be valid. |
Signature Algorithm | Select an algorithm to encrypt your signature. You can choose from SHA1 with DSA, SHA1 with RSA, MD5 with RSA, and RIPEMD160 with RSA. |
...
Click the Develop tab and then click Services > Security > Keystore/Truststore. This action will show you the Manage Keystore/Truststore screen (see Figure 365).
Figure 365: Manage Keystore/Truststore
Click the Create New link. This action will show you the Create New Keystore/Truststore screen (see Figure 366).
Figure 366: Create New Keystore/Truststore Screen
- To create a new keystore enter the name and description of the keystore activity in the Name and Description textboxes respectively.
- In the Create field, select the KeyStore radio button.
In the Creation Mode field, select the Upload radio button if you want to create a keystore by uploading a keystore file. Or select the Manual radio button if you want to manually configure a keystore.
Info If you select the Upload radio button then, follow step 6. Alternatively if you select the Manual radio button then, follow 7 - 10 steps.
In the Upload KeyStore field, select the Browse button. In the Choose File to Upload dialog box, navigate to your PKCS12 or JKS keystore file type and select the Open button to upload your keystore file.
If you select a keystore file with no extension then, from the Keystore Type dropdown list select the type of keystore (see Figure 367).
Figure 367: Keystore Type Dropdown List
- Enter the keystore password in KeyStore Password and Confirm Password text boxes.
- Enter the private key password in Private Key Password and Confirm Password text boxes.
Enter the values in all the fields as per your requirement and click Save. This action will create a keystore and the private public key pair inside the keystore ( see Figure 368).
Figure 368: Manually Configure A Keystore
- Click the Save button to save the keystore.
Info |
---|
The Adeptia Suite does not support keystore with multiple key entries. |
...
Click the Develop tab and then click Services > Security > Keystore/Truststore. This action will show you the Manage Keystore/Truststore screen (see Figure 369).
Figure 369: Manage Keystore/Truststore
Click the Create New link. This action will show you the Create New Keystore/Truststore screen (see Figure 370).
Figure 370: Create New Keystore/Truststore Screen
- To create a new truststore select the enter the name and description of the keystore activity in the Name and Description textboxes respectively.
- In the Create field, select the TrustStore radio button.
In the Upload TrustStore field, select the Browse button. In the Choose File to Upload dialog box, navigate to your JKS truststore file type and select the Open button to upload your truststore file.
Info Truststore only supports JKS file type.
- Enter the password to access a truststore in the TrustStore Password textbox.
Enter the confirmation password in the Confirm Password textbox.
Info When you upload a single certificate and enter a password for it then we are creating a truststore.
You can create a truststore with a single certificate.- Click the Save button to save the truststore.
Vault or Password Vault is a repository that keeps a collection of passwords at a secure location. Adding more security while saving a new password or accessing your stored passwords. Vault provides you with a robust security level.
Creating Vault
- Go to Develop > Services > Security > Vault.
- Click Create New.
Type the name and description of the new Vault.
As you type the name in Step3, Vault Alias field gets populated with the name of the vault by default. You can change the Alias name before you hit Save. Once saved, you cannot modify the Alias name.
Type a key and its value. By default a key with the user's login credentials are populated by default. You can replace them with new values.
Click Add to add a new Parameter.
- Click to view the masked passwords. The icon changes to . Click on this icon to mask the pasword again. You can delete any parameter by clicking in front of the particular parameter.
- Expand Advanced Properties to change the project and owner of this vault.
- Also provide permission of Read, Write and, Execute to Owner, Group and, Others. Note that Read permission is necessary if either Write or. Execute or, both is being given to any user group.
- Click Save.
Deleting Vaults
- Select checkbox in front of vault(s) you wish to permanently delete.
- Click Delete.
Adding Filters
You can sort any column ascending or descending based on your requirement.
- Hover the mouse over the desired column name. Click on down arrow that appears.
- Select Sort Ascending to sort the column entries in ascending order.
- Click Sort Descending to sort the column entries in descending order.
Show/Hide Columns
- Hover the mouse over the desired column name. Click on down arrow that appears.
- Scroll down to 'Columns' option to expand a list of Columns available to add in the view. Select the checkboxes for the columns you want to see in the view and uncheck the columns you don't want to see in the view.
Edit Vault
- Click the valult name or, Click next to the Vault you wish to edit, and select Edit.
- You can edit the information in the window that appears. Note that you cannot rename Alias once it is created. Other details that cannot be modified are 'Creation Date', 'Modified Date' and, 'Last Modified by'.
View Vault
- Click next to the Vault you wish to view.
Click 'View'. A new window will open up with information about the vault.
Property Significance Description Alias Name Parameter Json Entity ID Type ID Owner Owner's Group Creation Date Last Modified Date Last Modified By Permissions Revision Sunchronized Activity Project
Check in vault
- Click next to the desired Vault and select 'Check in'
- Add a comment (optional) in the window that appears and click 'Commit'
- A status window appears notifying the checkin status and revision number where the particular vault activity is checked in. Cick OK.
Vault Status
Three different Icons depict the status of Vaults and are displayed next to the vault name in the list. Following table shows the icons and their significance
Icon | Significance |
---|---|
The vault is not in Version Control | |
The vault is modified on latest revision revision_number | |
The vault is synchronized with the latest revision revision_number |
Revision History
- Click next to the desired Vault and select 'Revision History'
- A window with revision history opens for the particular vault.