FlexDeploy provides out of box integration with CyberArk AAM to retrieve secrets. FlexDeploy will authenticate using client certificate or retrieve credentials using Agent. In this section we will talk about client certificate based authentication.
Here are some steps for creating a client .pem file for authenticating against CyberArk from FlexDeploy. This uses openssl to create a certificate signing request and private key. Your organization may have their own guidelines, but this may help for understanding the general process needed.
This set of steps will create a PKCS#8 key file. See Converting Between Key Formats if you prefer another format.
You must first create Credential Store in FlexDeploy by clicking Create Store button on Administration - Security - Credentials page. Credential store represents instance of specific type of credential store provider. If you have more than one CyberArk AAM installations, you will create equal number of Credential Stores in FlexDeploy. Use CyberArk AAM Provider when creating this store.
Here are the configurations necessary for this store.
Property Name | Notes | Example |
---|---|---|
CyberArk URL | HTTP URL for CyberArk AAM. FlexDeploy will invoke HTTP GET to retrieve credential. If you use https protocol, then you may have to setup Server Certificate Path. URL can be https://services-xyz.skytap.com:1234 or https://services-xyz.skytap.com:1234/AIMWebservice/api/Accounts. If URL does not end with api/Accounts, then /AIMWebservice/api/Accounts will be added to end of URL automatically for invocation. | https://services-xyz.skytap.com:1234 |
Client Certificate Path | This is the full path to the .pem file containing the private key and certificate chain used to authenticate FlexDeploy against CyberArk AAM. Only PEM certificates are supported at this time. You must store PEM certificate file with private key and certificate on FlexDeploy server in secure location. See the Supported Key Formats section below to verify your private key meets requirements. | |
Client Certificate Password | Client certificate password. This is required for encrypted private keys. | |
Server Certificate Path | Optional, only needed if using https protocol. This is the full path to the .pem certificate file which is used to setup trust for CyberArk server. Only PEM certificates are supported at this time. You must store PEM certificate file with certificate on FlexDeploy server in secure location. |
Now you are ready to create individual credential to be retrieved from CyberArk.
You can create or edit credentials from Credentials page or from where specific credential is used.
CyberArk credential requires two inputs as described below.
Input Name | Notes |
---|---|
Application Id | Application id and Query Text are used to retrieve secret from CyberArk AAM. |
Query | Query Text for credential. For example, Safe=Linux%20Accounts;Folder=root;Object=secret |
Here is how edit credential looks like.
Create credential looks similar except you need to provide Scope as well. Scope can not changed once credential is saved.
You can change credential inputs (Application Id, Query Text) at any point. FlexDeploy will use these inputs with credential store properties like URL, Certificate Path etc. to retrieve individual credential for use during Workflow Execution.
Often, a certificate and key will be provided in the form of .cer and .key files or some other format. OpenSSL or another tool will be needed to convert to the supported PEM format. See some examples below.
openssl pkcs12 -export -in <.cer file> -inkey <.key file> -out <.p12 result file> -name <friendly name>
openssl pkcs12 -in <.p12 file> -out <.pem result file>
openssl rsa -in <.pem file> -out <rsa .pem file>
openssl pkcs12 -export -in <.pem file> -out <.p12 file>
openssl pkcs12 -in <.p12 file> -out <new .pem file>