Create credentials and test credential encryption
Create a credential to authenticate into a third-party system.
Avant de commencer
Role required: admin, KMF_admin, sn_secrets.secret_manager, and sn_kmf.cryptographic_manager
Important :
The logged in user of the MID Server also is required to have the following roles: admin, KMF_admin, sn_secrets.secret_manager, and sn_kmf.cryptographic_manager.
Procédure
- Navigate to the SSH credentials list by entering ssh_credentials.list in the navigation filter.
- Select New to create an SSH credential record.
-
In the form, fill in the following fields.
Tableau 1. SSH credential form Field Value Name Enter a name for your credentials record. This name can be any value you want. Applies to Select Specific MID Servers MID Servers Select your MID Server. User name Enter the user name. Password Enter the password related to the user in the User name field. -
Select the lock icon (
) next to the Credential alias field.
-
Select the reference icon (
) to open the Connection & credential aliases list.
- Select New to create a Connection & credential alias record.
- Enter a name in the Name field.
- Select Credential in the Type field.
-
Select Submit.
You’re returned to the SSH Credentials record. In the next steps, you test that the credential is encrypted.
- Select and hold (or right-click) the form header and select Show XML.
-
Find the
<password>XML tag within the XML. -
Copy the sys_id within this
<password>tag to your clipboard.The sys_id is a 32 character code representing the symmetric key that is being used to encrypt this credential. The encrypted password that you entered into the SSH Credentials table is to the right of the two sets of boxes on this same line. - Navigate to the Module keys list by entering sys_kmf_module_key.list in the navigation filter.
-
Filter the list for records where the Sys ID field matches the sys_id you copied in step 12, and select Run.
Your search should return a single Module key record. This record shows you that you have successfully created, and are using, a symmetric key.
- Navigate to the Wrapped module keys list by entering sys_kmf_wrapped_module_key.list in the navigation filter.
-
Filter the list for records where the Crypto module field matches the cryptographic module you created in the earlier steps, and select Run.
Your search should return a single Wrapped module key record. From this list you can verify the following:
- The Wrapped key material column shows that the symmetric key within the Crypto Module (that is being used to encrypt the SSH credential) is encrypted by the public key that you uploaded to the Identity Group.
- The Wrapped key sys id field shows that it's the key (the Crypto Module symmetric key) that is being encrypted by the Wrapping key sys id (the Public Key uploaded to the Identity Group).
If the preceding fields aren't on your list by default, you can add them to the list by selecting the Personalize list icon (
).
Remarque :Your instance executes a clean-up job every 10 minutes, which removes orphaned keys and helps prevent unassociated key proliferation after you update your credentials.