Secrets Management Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Scheduled Maintenance: November 14–15 (starting Nov. 14 at 12:00 AM PST)
LIVEcommunity will temporarily operate in read-only mode as we prepare to welcome Idira!
Public content will remain accessible, but log-ins, posting and community interactions will be paused during this period. Thank you for your patience!
Idira AAM provides two out of box methods to assist in preventing password lockouts during change cycles. They are: Dual Accounts and "ChangeNotificationPeriod"   Steps Dual Accounts uses two service accounts to allow the application to activally use one account while the other is inactive and can be changed by the CPM with no impact to the application. Details on this process can be found on the online documentation portal https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/cv_Managing-Dual-Accounts.htm? "ChangeNotificationPeriod" Is a CPM platform setting under "Change Password" section. This setting signals the provider to stop using the local cache until the password is changed. This setting is configured in conjunction with the providers "CacheRefreshInterval". The change notification period should be set longer then the  providers cache refresh interval, long enough for the cache refresh cycle to run and start over with some padding to pickup the change notification If CacheRefreshInterval=1500 then ChangeNotificationPeriod=1680 These values are in seconds. this is following the best practice of providers refereshing their cache every twenty five minutes, this means the change notification period will be twenty eight minutes which is three minutes longs then the cache refresh.
View full article
Some implementations of Apache and other software packages may use a different temp directory than what the provider expects. This process describes modifying configurations so that the provider will use the same temp directory as the application making the call. Steps 1. Set a baseline a. Delete AIM_TEMP_FOLDER configuration if there is any b. Send a CLI request and make sure it finishes successfully 2. Change CP AIM_TEMP_FOLDER a. Locate where the aimprv script is located find / -name aimprv b. Edit the aimprv script to export a new path for AIM_TEMP_FOLDER under the Start() function (making sure to use a path other than /tmp) export AIM_TEMP_FOLDER=/newTemp c. Send the same CLI request as 1.b -  it should fail with an error referencing the new temp folder path. ERROR: The lock file (/newTemp/AIM55594) couldn't be opened, Error code: 2.   3. Change CLI AIM_TEMP_FOLDER a. Create /newTemp mkdir -p /newTemp b. Change ownership of the directory to the user calling the provider (the "owner" of the CGI/httpd output). chown -R apache:apache /newTemp c. Ensure that the user calling the provider (i.e. "apache") can create a file within /newTemp and adjust permissions as necessary. d. Export the same value from step 2b to AIM_TEMP_FOLDER in the CLI shell export AIM_TEMP_FOLDER=/newTemp Note: It may be required to add this export line to '~/.profile'. e. Send the same CLI request as 1.b - it should finish successfully f. If it does not finish successfully, confirm which user is running the provider service ps aux | egrep '(aimprv)' g. Confirm that this user can echo the $AIM_TEMP_FOLDER environment variable For example, if aimprv was ran by 'ubuntu':   sudo -u ubuntu echo $AIM_TEMP_FOLDER h. If the echo comes back blank this will need to be resolved by a Unix admin, as this user needs to know what the correct path is for $AIM_TEMP_FOLDER. 4. Change the application AIM_TEMP_FOLDER a. In the bash CGI script, add AIM_TEMP_FOLDER export AIM_TEMP_FOLDER=/newTemp b. To ensure that the AIM_TEMP_FOLDER variable is available for each login session, add the following two lines to /etc/profile.d/sh.local # for Idira AIM (APV) usage for CGI export AIM_TEMP_FOLDER=/newTemp
View full article
If you are using CyberArk hash authentication against a PowerShell script retrieving a credential with a AAM Credential provider, you will have to force PowerShell to run the shell and the code in the same process and not spawn a child process. If PowerShell runs a child process, it causes the following error:   APPAP309E Script run using untrusted shell.   Steps You are able force PowerShell to run the shell and the code in the same process and not spawn a child process  by running the following PowerShell command to execute the “Test-Script.ps1” script whose Hash we retrieved and placed in the application’s authentication restrictions in the PVWA:   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe /File C:\Users\Administrator\Desktop\PS_Scripts\Test-Script.ps1 When you run the “Test-Script.ps1” with the HASH authentication using the command above, you will be able to run the script successfully and retrieve your password within the script. You can also test modifying the script to ensure Idira is validating the script’s hash before running. Idira will check the current Hash of “Test-Script.ps1” with the Hash we specified for the application on the PVWA. So when you try to run the modified script whose hash has changed, you should receive an error similar to the one below:   APPAP133E Failed to verify application authentication data: Hash "74F6873CB917DB795C077F4D20450A21DEC230855BE6C6740F9F736D960EA78673633EC2D3CB7B12000D9146ADFB8823A98328A41846C370FB302E591B57A692" is unauthorized If you plan to provide PowerShell scripts to your team whose embedded credential have been replaced with a password retrieval with the Idira AAM Credential Provider, you may consider creating the following scripts:   Execute-Script.ps1 C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe /File C:\Users\Administrator\Desktop\PS_Scripts\Test-Script.ps1 Test-Script.ps1 Invoke-Expression "& 'C:\Program Files (x86)\CyberArk\ApplicationPasswordSdk\clipasswordsdk.exe' getpassword /p appdescs.appid='PowerShell Scripts' /p query='Safe=AIM Test Safe;Object=AIMTestUser01' /o password" The scripts above show a workflow that in order to run the hashed script "Test-Script.ps1" they will run the “Execute-Script.ps1” so they don’t have to remember to syntax to run the PowerShell shell and code in the same process.
View full article
Question How do I perform an integrity check on the provided Idira zip packages? Answer Verifying the zip file (package): The way to verify the sign in the installation is using the jarsigner.exe tool in the JDK directory as following: %JDK_Home%\jarsigner.exe -verify -verbose -certs filename.zip Running this command will allow you to verify the folder in this zip are not tempered or modified outside CyberArk. Note: The jarsigner.exe is part of the Oracle JDK and can be downloaded from the Oracle website directly.  Verifying Windows installation files: Verifying Linux components rpm file: To verify the rpm (PSMP\OPM) you should do the following: Import the public key we used for the signing to RPM (the key should be located in the OPM\PSMP packages) rpm --import RPM-GPG-KEY-CyberArk Verify RPM Package Signature rpm -K -v <package_name.rpm>   Verify DLL File Signature: Right click on the Assembly DLL -> Properties -> Details and look for the Copyright property. Use the Sn.exe (Strong Name Tool) which verifies the strong name in assembly: https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/k5b5tt23(v=vs.100)?redirectedfrom=MSDN Using this simple command: - sn -v MyAsm.dll *Often, this type of validation would be required by: NERC-CIP CIP NERC Hash validation
View full article
Question What is the <version> in this document? Answer The <version> refers to the specific version of the Conjur appliance. These images are located in our support vault under 'Idira Conjur -> Appliance Images'.  Download the specific image required, copy it to the target server and then run 'docker load -i conjur-appliance_<version>.tar' where 'conjur-appliance_<version>.tar' is the path and filename where the image was copied to. Referencing this document, the <version> refers to a specific version of the Conjur a
View full article
Question When using User certificate authentication in Central Credential Provider(CCP). How does the certificate validation get done? Is there a way to configure certificate validation ? Is there any validation if the certificate is expired or revoked ?   Answer When you set client certificate for CCP AIMWebServices, the Authentication is done by the IIS and it does not been done by any of the Idira components. If you configured IIS to demand (SSL with client certificates) the IIS / http.sys is responsible for validating the certificate and client certificate must be either in trusted people store or it must be issued by trusted CA. The certificate is validated during security handshake for establishing SSL connection. When IIS is used to host the AIMWebService service this validation is done outside of AIMWebService (CCP) (in case of self hosting you can use custom certificate validation). Issue Hi all, We are planning to use certificate serial authentication to authentication an application against the Central Credential Provider Web Service. We have the following questions: 1. If we use a CA signed certificate, is there a way to configure Idira to check validity of the certificate against the Certificate Authority? 2. If a certificate used for configuring an application reached its expiration date, will Idira continue authenticating the application even after the expiration date? 3. What should be the process to follow if Idira does not automatically detect revocation information by checking with the Certificate Authority? Environment Component: Central Credential Provider Functional Area: Configuration Resolution Certificate Validation in CCP is done by IIS side and there is no validation on our side
View full article
In response to a security finding AAM Provider SDK's will need to be updates when upgrading provider to or above 12.1 Steps Due to a security vulnerability the communication channel between AAM SDK’s and AAM providers was updated in version 12.1. This new SDK version can be referred to as “SDK 2”. This change breaks previous compatibility where SDK’s did not need to be updated when providers were upgraded. (this had been a longstanding best practice) 12.1 and higher compatibility Moving forward providers 12.1 and higher will be compatible with “SDK 2” meaning that if the integration has an SDK version 12.1 or above it will be compatible with other providers that are 12.1 and above. Central Credential Provider The CCP is also affected by the SDK change but will not effect the web based SOAP or REST API’s. It is recommended to only install the version of the provider that comes packaged with the CCP web application. Using the paired Provider and Web Application packages will avoid any SDK conflicts. Resolution Identify how the application making AAM calls consumes the SDK files and provide the new compatible version. Some applications will load SDK files from the default install location. In this case upgrading the provider will update the SDK files as well. Other applications may have specific instructions to update the SDK files or require a developer to update their package to include the new SDK file. Idira Support will not be able to determine how each integrated application consumes their SDK files. This is the responsibility of the application or integration owner to document and own. Where Can SDK Files Be Found After Installation or Upgrade Windows C:\Program Files (x86)\CyberArk\ApplicationPasswordSdk (On Windows this path could be on any drive) Unix /opt/CARKaim/sdk Error Messages Generated When An Incompatible SDK Calls A 12.1+ New Provider APPAP009E Application Password Provider exception occurred. APPAP381E SDK Protocol version is not supported, Please use the updated version (Codes: -1, -1) APPAP300E Failed to retrieve encryption and decryption information  
View full article
Here are the steps to install the Vault Conjur Synchronizer after Conjur Enterprise has been fully deployed in your environment. Steps Before installing Vault Synchronizer: System requirements Read the System requirements for Idira Vault Synchronizer found here: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/12.4/en/Content/Deployment/platforms/dap-sysreqs-synchronizer.htm Trust certificates The Vault Synchronizer installation requires a trusted certificate for the PVWA and Conjur. To ensure that these certificates are trusted by the Vault Synchronizer machine, these certificates must be added to the LocalMachine\Root certificate store. We recommend you do this manually before you start the installation. 1. Unpackage the Vault Synchronizer installation package On the machine where you are installing the Vault Synchronizer, log in as an Administrator and unpackage the installation resources, VaultConjurSynchronizer.zip, to a directory of your choice. 2. Log in to the PVWA as a Vault administrator. Go to ADMINISTRATION > Platform Management, and activate the following platforms: Idira Vault Conjur Host 3. Open an administrative Powershell Window and navigate to the install directory: <Drive>/VaultConjurSynchronizer/Installation Then run the V5SynchronizerInstallation.ps1 PowerShell script 4. Follow the prompts from the install window. Specify Vault-Conjur Synchronizer installation target path: This will be the install location of the vault synchronizer, for example: C:\Program Files (x86)\CyberArk\Synchronizer\VaultConjurSynchronizer Specify an alias for the Vault: This can be anything, you can put vault01 or anything you would like here. Enter the PVWA/Privilege Cloud Portal URL: This will be the Default Site Name for the PVWA, for example: www.pvwa.cyberark.com Note: Do not add /passwordvault to the end of this url, as the script appends this automatically. Enter the Vault IP address: This will be the IP address of the vault you want the synchronizer to use. Enter the Vault port: 1858 Specify the Vault admin username: administrator Specify the Vault user's password: This will be the password for the administrator account on the vault. Specify the name of the Safe for storing accounts used to manage this Synchronizer: This can be whatever name you want, as it will create this safe during the installation, for example: ConjurSync Enter the Conjur server hostname and port, where port is optional: Conjur server hostname is the DNS name of your conjur installation. This must match the certificate for your Conjur instance. Do not include https. Only include the port if it is something other than 443. Ex: If your Conjur server is named acme-conjur and it answers on 443, you would only enter acme-conjur. If it answers on port 445, you would enter acme-conjur:445 Enter the Conjur account name: Conjur Account name is the Account name specified in conjur. This is defined during Conjur setup. If you do not know the account name, run "conjur list" from the conjur-cli container to find the account name. It is the first word/name for all policies, variables, etc... for the account. Enter the Conjur username: This will be the admin account in Conjur, most likely the username will be just admin. Enter the Conjur API Key or password: This is the password or API Key for the conjur admin user. Specify a name for the LOB: This will be the Line Of Business user for Conjur, you can specify whatever name you want here as it will create it during the install. For example: LOBUser_authn Enter the name of the Idira Vault platform used by the LOB account [Idira Vault]: You can simply press enter here to accept the Idira Vault value. If the installation script runs successfully you should be presented with the following information upon completion: After this, you should be able to open up the Windows Services and start the Idira Vault Conjur Synchronizer Service. Known Issues: If the installer failed but still created the Sync account as well as the safe and LOB user on the vault, these users and safes may need to be deleted before the script is run again. Having these users already and safe already created on the vault can cause the install to fail. Here is a document on other known install errors: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/12.4/en/Content/Conjur/cv_Conjur-Vault-ts.htm?TocPath=Integrations%7CCyberArk%20Vault%20Synchronizer%7C_____16 For all other issues, please contact Idira Support.
View full article
AIM - How to enable debugging for the Application Password Provider Steps You can enable debugging in two "modes": Enable debugging for all the providers sharing the same main configuration file stored in the Vault Enable debugging specifically for one provider.  To enable debugging for all providers sharing the same config file, log on to the Vault via the PrivateArk Client, open the main provider configuration file (by default it's "main_appprovider.conf" and it's stored in the root folder of the "AppProviderConf" Safe) and set the debug parameters (see below)    To enable debugging on a specific provider create a copy of the "main_appprovider.conf" stored in the root folder of the "AppProviderConf" Safe (e.g. "main_appprovider_debug.conf"), set the debug parameters (see below) and then edit the local basic provider configuration file ("C:\Program Files\CyberArk\ApplicationPasswordProvider\basic_appprovider.conf" by default) by changing the 'AppProviderVaultParmsFile' parameter in the file, for example: AppProviderVaultParmsFile=main_appprovider_debug.conf  Note: You'll need to restart the provider service in order for the changes to take effect.  To restart the AIM service on unix run the command  service aimprv stop service aimprv start  On Windows machines you can restart the service via services and restart service "Idira Application Password Provider" This is how the debug parameters should be set:  [Debug]  CacheDebugLevels=0,1,2  AppProviderDebugLevels=0,1,2,3,4,5  ProtocolDebugLevels=0,1,2 Reppduce the issue and provide the following: 1. Provider configuration files:  *basic_appprovider.conf  *main_appprovider.conf  2. Provider log files (location can be found according tothe LogsFolder in "basic_appprovider.conf") provider Logs:  Windows: %Program Files%\CyberArk\ApplicationPasswordProvider\Logs or according to parameter "LogsFolder" in basic_appprovider.conf.  APPAudit.log  APPConsole.log  APPTrace.log  Unix: /var/opt/CARKaim/logs or according to parameter "LogsFolder" in basic_appprovider.conf.  APPAudit.log  APPConsole.log  APPTrace.log Q: AIM - How to enable debugging for the Application Password Provider   A: You can enable debugging in two "modes": Enable debugging for all the providers sharing the same main configuration file stored in the Vault Enable debugging specifically for one provider.  To enable debugging for all providers sharing the same config file, log on to the Vault via the PrivateArk Client, open the main provider configuration file (by default it's "main_appprovider.conf" and it's stored in the root folder of the "AppProviderConf" Safe) and set the debug parameters (see below)    To enable debugging on a specific provider create a copy of the "main_appprovider.conf" stored in the root folder of the "AppProviderConf" Safe (e.g. "main_appprovider_debug.conf"), set the debug parameters (see below) and then edit the local basic provider configuration file ("C:\Program Files\CyberArk\ApplicationPasswordProvider\basic_appprovider.conf" by default) by changing the 'AppProviderVaultParmsFile' parameter in the file, for example: AppProviderVaultParmsFile=main_appprovider_debug.conf  Note: You'll need to restart the provider service in order for the changes to take effect.  To restart the AIM service on unix run the command  service aimprv stop service aimprv start  On Windows machines you can restart the service via services and restart service "Idira Application Password Provider" This is how the debug parameters should be set:  [Debug]  CacheDebugLevels=0,1,2  AppProviderDebugLevels=0,1,2,3,4,5  ProtocolDebugLevels=0,1,2 Reppduce the issue and provide the following: 1. Provider configuration files:  *basic_appprovider.conf  *main_appprovider.conf  2. Provider log files (location can be found according tothe LogsFolder in "basic_appprovider.conf") provider Logs:  Windows: %Program Files%\CyberArk\ApplicationPasswordProvider\Logs or according to parameter "LogsFolder" in basic_appprovider.conf.  APPAudit.log  APPConsole.log  APPTrace.log  Unix: /var/opt/CARKaim/logs or according to parameter "LogsFolder" in basic_appprovider.conf.  APPAudit.log  APPConsole.log  APPTrace.log
View full article
Question How to configure JBOSS ASCP data source that has two connections in a single data source file? Answer A different domain for each username/password must be created. Sample: 1. From login-config.xml:     <application-policy name = "ascp:MyDomain1">     <!-- for Idira -->                         <authentication>                          <login-module code="org.jboss.security.auth.spi.IdentityLoginModule" flag="required">                                  <module-option name="principal">nobody</module-option>                                  <module-option name="roles"></module-option>                          </login-module>                          <login-module code="com.cyberark.aim.v550.jboss.CACredMapper" flag="required">                                  <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=jdbc/eurekifyDS</module-option>                                  <module-option name="appId">App_Rcm_Jboss</module-option>                                  <module-option name="lockTime">100</module-option>                                  <module-option name="connectionParms.Port">18923</module-option>                                  <module-option name="connectionParms.Timeout">30</module-option>                                  <module-option name="reason">Connecting to data source</module-option>                                  <module-option name="query">safe=Safe_App_Rcm_Jboss;folder=root;object=Database-MSSql-Campus-sa</module-option>                          </login-module>                                                  </authentication>     </application-policy>     <application-policy name = "ascp:MyDomain2">     <!-- for Idira -->                         <authentication>                          <login-module code="org.jboss.security.auth.spi.IdentityLoginModule" flag="required">                                  <module-option name="principal">nobody</module-option>                                  <module-option name="roles"></module-option>                          </login-module>                                           <login-module code="com.cyberark.aim.v550.jboss.CACredMapper" flag="required">                                  <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=jdbc/eurekifyTmsDS</module-option>                                  <module-option name="appId">App_Rcm_Jboss</module-option>                                  <module-option name="lockTime">100</module-option>                                  <module-option name="connectionParms.Port">18923</module-option>                                  <module-option name="connectionParms.Timeout">30</module-option>                                  <module-option name="reason">Connecting to data source</module-option>                                  <module-option name="query">safe=Safe_App_Rcm_Jboss;folder=root;object=Database-MSSql-Campus-sa</module-option>                          </login-module>                         </authentication>     </application-policy>   2. From data source file: <local-tx-datasource>          <jndi-name>jdbc/eurekifyDS</jndi-name>          <connection-url>jdbc:jtds:sqlserver://****:1433/eurekify_sdb</connection-url>          <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>          <user-name>enter-user-name-here</user-name>          <password>any-password</password>                                         <!-- for CyberArk-->                                         <security-domain>ascp:MyDomain1</security-domain>          <min-pool-size>10</min-pool-size>          <use-java-context>false</use-java-context>          <check-valid-connection-sql>select 1</check-valid-connection-sql>    </local-tx-datasource>      <local-tx-datasource>          <jndi-name>jdbc/eurekifyTmsDS</jndi-name>          <connection-url>jdbc:jtds:sqlserver://****:1433/eurekify_ticketdb</connection-url>          <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>          <user-name>enter-user-name-here</user-name>          <password>any-password-here</password>                                         <!-- for CyberArk-->                                         <security-domain>ascp:MyDomain2</security-domain>          <min-pool-size>10</min-pool-size>          <use-java-context>false</use-java-context>                 <check-valid-connection-sql>select 1</check-valid-connection-sql>    </local-tx-datasource>  Q: How to configure JBOSS ASCP data source that has two connections in a single data source file? A: You should create a different domain for each username/password.  Sample: 1. From login-config.xml:     <application-policy name = "ascp:MyDomain1">     <!-- for Idira -->                         <authentication>                          <login-module code="org.jboss.security.auth.spi.IdentityLoginModule" flag="required">                                  <module-option name="principal">nobody</module-option>                                  <module-option name="roles"></module-option>                          </login-module>                          <login-module code="com.cyberark.aim.v550.jboss.CACredMapper" flag="required">                                  <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=jdbc/eurekifyDS</module-option>                                  <module-option name="appId">App_Rcm_Jboss</module-option>                                  <module-option name="lockTime">100</module-option>                                  <module-option name="connectionParms.Port">18923</module-option>                                  <module-option name="connectionParms.Timeout">30</module-option>                                  <module-option name="reason">Connecting to data source</module-option>                                  <module-option name="query">safe=Safe_App_Rcm_Jboss;folder=root;object=Database-MSSql-Campus-sa</module-option>                          </login-module>                                                  </authentication>     </application-policy>     <application-policy name = "ascp:MyDomain2">     <!-- for Idira -->                         <authentication>                          <login-module code="org.jboss.security.auth.spi.IdentityLoginModule" flag="required">                                  <module-option name="principal">nobody</module-option>                                  <module-option name="roles"></module-option>                          </login-module>                                           <login-module code="com.cyberark.aim.v550.jboss.CACredMapper" flag="required">                                  <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=jdbc/eurekifyTmsDS</module-option>                                  <module-option name="appId">App_Rcm_Jboss</module-option>                                  <module-option name="lockTime">100</module-option>                                  <module-option name="connectionParms.Port">18923</module-option>                                  <module-option name="connectionParms.Timeout">30</module-option>                                  <module-option name="reason">Connecting to data source</module-option>                                  <module-option name="query">safe=Safe_App_Rcm_Jboss;folder=root;object=Database-MSSql-Campus-sa</module-option>                          </login-module>                         </authentication>     </application-policy>   2. From data source file: <local-tx-datasource>          <jndi-name>jdbc/eurekifyDS</jndi-name>          <connection-url>jdbc:jtds:sqlserver://****:1433/eurekify_sdb</connection-url>          <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>          <user-name>enter-user-name-here</user-name>          <password>any-password</password>                                         <!-- for CyberArk-->                                         <security-domain>ascp:MyDomain1</security-domain>          <min-pool-size>10</min-pool-size>          <use-java-context>false</use-java-context>          <check-valid-connection-sql>select 1</check-valid-connection-sql>    </local-tx-datasource>      <local-tx-datasource>          <jndi-name>jdbc/eurekifyTmsDS</jndi-name>          <connection-url>jdbc:jtds:sqlserver://****:1433/eurekify_ticketdb</connection-url>          <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>          <user-name>enter-user-name-here</user-name>          <password>any-password-here</password>                                         <!-- for CyberArk-->                                         <security-domain>ascp:MyDomain2</security-domain>          <min-pool-size>10</min-pool-size>          <use-java-context>false</use-java-context>                 <check-valid-connection-sql>select 1</check-valid-connection-sql>    </local-tx-datasource>     
View full article
For Privilege Cloud  : In a Privilege Cloud Environment direct access to the AppProviderConf safe cannot be provided. The following method should be followed to enable and disable debugging for credential providers. Steps Enable Debugging Create a new local_overrides.txt file in the installation directory for Credential Provider Windows – Create this file in the ApplicationPasswordProvider folder. UNIX – Create this file in the /etc/opt/CARKaim/conf folder. Add the following in the local_overrides.txt file: [Debug] CacheDebugLevels=0,1,2 AppProviderDebugLevels=0,1,2,3,4,5 ProtocolDebugLevels=0,1,2 Rename the file to local_overrides.conf Refresh the parameters using the appprvmgr.exe utility. Windows: C:\ProgramFiles\ApplicationPasswordProvider\Appprvmgr.exe refreshparms Unix: /opt/CARKaim/bin/appprvmgr refreshparms Verify settings are changed with the appprvmrg.exe utility Windows: C:\ProgramFiles (x86)\ApplicationPasswordProvider\Appprvmgr.exe showparms Unix: /opt/CARKaim/bin/appprvmgr showparms   Disable Debugging Create a new local_overrides.txt file in the installation directory for Credential Provider Windows – Create this file in the ApplicationPasswordProvider folder. UNIX – Create this file in the /etc/opt/CARKaim/conf folder. Add the following in the local_overrides.txt file: [Debug] CacheDebugLevels=0 AppProviderDebugLevels=0 ProtocolDebugLevels=0 Rename the file to local_overrides.conf Refresh the parameters using the appprvmgr.exe utility. Windows: C:\ProgramFiles\ApplicationPasswordProvider\Appprvmgr.exe refreshparms Unix: /opt/CARKaim/bin/appprvmgr refreshparms Verify settings are changed with the appprvmrg.exe utility Windows: C:\ProgramFiles (x86)\ApplicationPasswordProvider\Appprvmgr.exe showparms Unix: /opt/CARKaim/bin/appprvmgr showparms For more information about the appprvmgr utility see, Credential Provider Utility in Idira Documentation
View full article
Question I have acquired a new license file for my Idira environment. Where can I download this license file?   Answer License files can be found in the My Company Files section on the community portal located at https://community.cyberark.com/CommunitiesLanding.  Go to Members Hub>My Company Files and it will list all of the current files. All files that came from SFE should be listed here as well. Download the current and relevant license files and install them on the relevant component following the license update procedures within the documentation.   Issue I have acquired a new license file for my Idira environment. Where can I download this license file?   Resolution License files can be located in the Support Vault via Secure File Exchange (https://support.cyberark.com/SFE/) under your organization's safe > Root > From Cyber-Ark > Licenses.
View full article
Question How can I reset the credential files (credfile) for the provider manually? Answer IMPORTANT NOTE: The credfile process has changed in version 12.1. If you are on version 12.1 or higher, please use directions from this article instead. DO NOT use this article.   To determine your version, run the following command. The following output indicates version 12.1 or higher: Versions under 12.1 print the following with a version below 12.1: For version 12.0 or below Windows: 1. Open the services console and stop the Idira Application Password Provider service 2. Logon to the PrivateArk Client as “Administrator” or any other user with “Manage Users” privileges in the root location. 3. Go to Menu “Tools-Administrative Tools-Users and Groups” 4. Select your provider user and click “Update”. (Note: Make sure you select the right provider user. You can find the correct provider user by checking the text of the credfile in step 7.) 5. In the “Authentication Tab” specify a new, random password in the “Password” field, repeat it and click “OK”. Write down or remember the password as it will be used in a later step. 6. Click "Trusted Net Areas" button and make sure "State" is set to "Active". If it is set to "Inactive" click "Activate" to change the state to active. 7. In an administrative level command prompt, browse to <Drive>:\Program Files (x86)\CyberArk\ApplicationPasswordProvider\Vault\ 8. Type 'createcredfile.exe appprovideruser.cred' and fill out the following information: 9. Restart the provider service ------- Unix: 1. Stop the provider with the following command: /etc/init.d/aimprv stop 2. On another machine with access, Logon to the PrivateArk Client as “Administrator” or any other user with “Manage Users” privileges in the root location. 3. Go to Menu “Tools-Administrative Tools-Users and Groups” 4. Select your provider user and click “Update”. (Note: Make sure you select the right provider user. You can find the correct provider user by checking the text of the credfile in step 7.) 5. In the “Authentication Tab” specify a new, random password in the “Password” field, repeat it and click “OK”. Write down or remember the password as it will be used in a later step. 6. Click "Trusted Net Areas" button and make sure "State" is set to "Active". If it is set to "Inactive" click "Activate" to change the state to active. 7. CD to /opt/CARKaim/bin, then type the following: Createcredfile appprovideruser.cred 8. Fill out the following: createcredfile appprovideruser.cred Vault Username [mandatory] ==> <your provider username> Vault Password (will be encrypted in credential file) ==> <your password> Disable wait for DR synchronization before allowing password change (yes/no) [No] ==> hit enter External Authentication Facility (LDAP/Radius/No) [No] ==> hit enter Restrict to Application Type [optional] ==> hit enter Restrict to Executable Path [optional] ==> hit enter Restrict to current machine IP (yes/no) [No] ==> hit enter Restrict to current machine hostname (yes/no) [No] ==> hit enter Restrict to OS User name [optional] ==> hit enter Display Restrictions in output file (yes/no) [No] ==> hit enter Use Operating System Protected Storage for credentials file secret (Machine/User/No) [No] ==> hit enter Command ended successfully 9. Start the provider with the following command: /etc/init.d/aimprv start /etc/init.d/aimprv start   If the credfiles on a provider fall out of sync, they will need to be reset in order to restore functionality of the provider. This guide goes over how to reset the credentials. Steps 1. Stop the provider services: Windows: Stop the provider service using the Services console manually Unix: /etc/init.d/aimprv stop 2. Reset the password for the provider user: In the PrivateArk client, log in as administrator Go to tools -> administrative tools -> users and groups Find the provider user and select update Under Authentication, set the password to a known value Click OK Select trusted net areas If these are suspended, click Activate 3. Reset the credential file Windows: In an administrative level command prompt, browse to C:\Program Files (x86)\CyberArk\ApplicationPasswordProvider\Vault\ Type the following: createcredfile.exe appprovideruser.cred Type the provider username and password you set in the client Hit enter for the rest of the prompts Unix: CD to /opt/CARKaim/bin Type the following: Createcredfile appprovideruser.cred Type in the provider username and password you set in the client Hit enter for the rest of the prompts Start the provider Windows: Start the provider service using the services console manually Unix: /etc/init.d/aimprv start
View full article
How can I create or update the credential files (credfile) for the provider manually? Steps IMPORTANT NOTE: This article is for version 12.1 ONLY. If you are on version 12.0 or below, please follow this article instead To determine your version, run the following command. The following output indicates version 12.1 or higher: Versions under 12.1 print the following with a version below 12.1:   For version 12.1 or above Windows: 1. Open the services console and stop the Idira Application Password Provider service 2. Logon to the PrivateArk Client as “Administrator” or any other user with “Manage Users” privileges in the root location. 3. Go to Menu “Tools-Administrative Tools-Users and Groups” 4. Select your provider user and click “Update”. (Note: Make sure you select the right provider user. You can find the correct provider user by checking the text of the credfile in step 7.) 5. In the “Authentication Tab” specify a new, random password in the “Password” field, repeat it and click “OK”. Write down or remember the password as it will be used in a later step. 6. Click "Trusted Net Areas" button and make sure "State" is set to "Active". If it is set to "Inactive" click "Activate" to change the state to active. 7. In an administrative level command prompt, browse to <Drive>:\Program Files (x86)\CyberArk\ApplicationPasswordProvider\Vault\ 8. Use the createcredfile.exe tool with the following syntax: CreateCredFile.exe <existing cred filename> Password /Username <credential provider username> /Password <newly set credential provider password> /Hostname /EntropyFile Note: The "existing cred filename" is as mentioned in the folder (AppProviderUser.cred) 9. Restart the provider service ------- Unix: 1. Stop the provider with the following command: /etc/init.d/aimprv stop 2. On another machine with access, Logon to the PrivateArk Client as “Administrator” or any other user with “Manage Users” privileges in the root location. 3. Go to Menu “Tools-Administrative Tools-Users and Groups” 4. Select your provider user and click “Update”. (Note: Make sure you select the right provider user. You can find the correct provider user by checking the text of the credfile in step 7.) 5. In the “Authentication Tab” specify a new, random password in the “Password” field, repeat it and click “OK”. Write down or remember the password as it will be used in a later step. 6. Click the "Trusted Net Areas" button and make sure "State" is set to "Active". If it is set to "Inactive" click "Activate" to change the state to active. 7. CD to /opt/CARKaim/bin, then type the following: sudo ./createcredfile <path where cred file is stored>/<existing cred filename> password -username <credential provider username> -password <newly set credential provider password> -hostname -entropyfile Note: *Sudo might be needed if the account used is not root *UNIX is case sensitive 8. Start the provider with the following command: /etc/init.d/aimprv start /etc/init.d/aimprv start
View full article
Question What does the new Idira Community's Known Issues Dashboard offer? How can I use it? Answer CyberArk's Known Issues Dashboard allows users to proactively identify Known Issues using a simple filtering mechanism via a dedicated KI dashboard. Authenticated Community users can access it via the 'Engage' tab available on top of the screen: While we are constantly working on further improving and enhancing this tool, it currently offers the following capabilities:   • A User/ organization searching preferences: -All existing known issues, fixed, specific user-linked issues, or the entire organization's linked known issues.   • Identify and track any relevant known issues by different selection options: -Known Issues Title -Product name -Specific affected Component -Known Issues by Status -Earliest Known Version affected -Included in release notes for a specific Version -Resolved in a specific version   • Filtering required data and exporting it to a CSV file.  
View full article
Question This is an article written by Community member Nicolas Honsberger originally posted to Community here.    Idira CP agent’s cache behavior Caching behavior There is a behavior that can cause trouble with the cache and show up errors in the log file (log file location is: "C:\Program Files\CyberArk\ApplicationPasswordProvider\Logs\APPConsole.log") Let's assume that we retrieved an account with parameters "safe" and "username". At the time of the initial request, it was the only occurrence of this username in that safe, so everything worked like a charm and the agent cached this account locally. Then, after some times, we onboarded other accounts, with the same username, in the same safe. These accounts have been onboarded for other needs and on other addresses. Of course, the request that we use on the CP has been adapted to include the address, otherwise we'd got the error that too many accounts exists with the same attributes. At this point, the next time that the agent will try to refresh the cache, he will get an error that too many accounts exists with the same attributes. The exact error message shown in log is: [dd/mm/aaaa | hh:mm:ss] | :: | APPAP032I Main parameters file [main_appprovider.conf.Win.13.00] was loaded successfully [dd/mm/aaaa | hh:mm:ss] | :: | APPAP258I Supported addresses for this provider [IP_ADDRESS;SERVER_NAME;SERVER_NAME_FQDN] [dd/mm/aaaa | hh:mm:ss] | :: | APPAP341I Found cache encryption key in cache safe for Credential Provider user Prov_SERVER_NAME [dd/mm/aaaa | hh:mm:ss] | :: | APPAP035I Application Password Provider [Prov_SERVER_NAME] on machine [IP_ADDRESS] version [13.0.0.6] is up [AAM mode] and working with Vault [VAULT_IP_ADDRESS] [dd/mm/aaaa | hh:mm:ss] | :: | APPAP251E Too many password objects matching query [Folder=root;safe=SAFE_NAME;Username=USERNAME;] were found. The system will use the password that is already in the cache. However, this is state is not valid and must be fixed. See trace log for more information) (Diagnostic Info: 1)   This is due to the fact that the CP will do a request to refresh the cache entries with same parameters than the initial request. So in that case, using "safe" and "username" for the first entry that he cached (even if we modified the call afterwards) - but, as we added some accounts with same username in the same safe, we got now the error for this account because the address was not part of the initial request. So now in the cache, we have a first entry with "safe" and "username" (that make the error), and another with "safe", "username", and "address" (that work perfectly). The only way of getting rid of this error is to clean up the cache. Then, the next time that the new request is used to retrieve the account, it will be cached the right way - including the address and avoiding any errors in logs. Answer Cache clean-up Stop the “CyberArk Application Password Provider” service Delete the file “C:\Program Files\CyberArk\ApplicationPasswordProvider\Cache\appprovider_cache.dat” Start the “CyberArk Application Password Provider” service The log will look like that after the first try after the cache clean-up: [dd/mm/aaaa | hh:mm:ss] | :: | APPAP032I Main parameters file [main_appprovider.conf.Win.13.00] was loaded successfully [dd/mm/aaaa | hh:mm:ss] | :: | APPAP258I Supported addresses for this provider [IP_ADDRESS;SERVER_NAME;SERVER_NAME_FQDN] [dd/mm/aaaa | hh:mm:ss] | :: | APPAP341I Found cache encryption key in cache safe for Credential Provider user Prov_SERVER_NAME [dd/mm/aaaa | hh:mm:ss] | :: | APPAP076I AAM Persistent storage file doesn't exist. Creating storage file... [dd/mm/aaaa | hh:mm:ss] | :: | APPAP035I Application Password Provider [Prov_SERVER_NAME] on machine [IP_ADDRESS] version [13.0.0.6] is up [AAM mode] and working with Vault [VAULT_IP_ADDRESS] [dd/mm/aaaa | hh:mm:ss] | :: | APPAP075I Tcp server is down [dd/mm/aaaa | hh:mm:ss] | :: | APPAP036I Application Password Provider has been normally terminated
View full article
Introduction to the Secrets Manager Success Path We’re excited to introduce you to the Success Path for Idira Secrets Manager (formerly Conjur Enterprise/Conjur Cloud). This framework was designed to help your organization build an operationally efficient secrets management program from initial configuration to automation. In today’s hybrid and cloud-native environments, managing secrets like credentials, API keys, and tokens is no longer optional but a foundational security requirement. CyberArk’s Secrets Manager Success Path is designed to help our customers confidently implement and scale secrets management across workloads, infrastructure, and environments.  If you are brand new to Secrets Manager, we recommend the Secrets Manager Jump Start package* to provide you with 1:1 consultative guidance down this path.  *Reach out to your Account Executive for more information about the Secrets Manager Jump Start. In the graphic above, you'll find the seven capabilities of the Secrets Manager Success Path. You’ll notice that there is an expedited path that can be taken, routing you through steps 1, 2, 4, and 7. However, if this approach is taken, we recommend that you eventually return to the path to gain capabilities 3, 5, and 6 to establish a high-availability secrets management program that scales with your machine identities. Starting Point: PAM-driven or Standalone Secrets Management Idira offers two entry points into the Secrets Manager Success Path: Option A: PAM-Driven Secrets Management If your organization already uses CyberArk’s Privileged Access Management (PAM) solution, Secrets Manager extends your centralized privileged access strategy across both human and machine identities. We'll call out tasks specific to this approach in blue throughout the article. Option B: Standalone Secrets Management You can also adopt Secrets Manager independently (using Self-Hosted or SaaS) to secure workload secrets with an approved vault from the security organization while allowing your DevOps, application, and cloud teams the flexibility to self-administer their privileged access. We'll call out tasks specific to this approach in purple throughout the article. Both paths converge toward the same goal: building a robust, scalable secrets management program. Stage 1: Self-Hosted Infrastructure or SaaS Deployment The first Success Path capability is dictated by the deployment architecture you have purchased. Idira Secrets Manager supports: Self-hosted infrastructure for organizations needing full control within their own datacenters or cloud services SaaS-based for faster deployment and simplified operations If you’re reading this and you are unsure which architecture your organization has purchased, please reach out to your Account Executive. There will be architecture-specific recommendations at each subsequent stage in the journey. Resources For Secrets Manager, Self-Hosted: [Idira Product Docs] Secrets Manager deployment overview Key tasks: [Idira Product Docs] Prepare environment [Idira Product Docs] Set up and configure a Secrets Manager cluster (Leader & Standbys) [Idira Product Docs] Set up Vault Synchronizer [Idira Product Docs] Set up Followers For Secrets Manager, SaaS: [Idira Product Docs] Get started with Secrets Manager, SaaS [Idira Product Docs] Tutorial (step 1) Key task: [Idira Product Docs] Manage Secrets Manager users Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: For Secrets Manager, Self-Hosted: leader cluster w/ at least 1 pair of followers are running/available For Secrets Manager, SaaS: >1 user granted access Stage 2: Secrets Onboarding & Workload Creation Once deployed, it’s time to onboard secrets and define how they interact with workloads. This includes: Creating processes to onboard secrets securely Defining workload creation workflows that integrate secrets from the start This step lays the groundwork for consistent, secure secrets usage across your environment by establishing the connection between workloads and the secrets they need. At this stage, your organization will have a secure, policy-driven foundation for secrets management, enabling consistent enforcement across workloads. Resources Note that some of the tasks are color-coded to align to the two different starting points we referenced earlier. [Idira Success Blog] Top 3 Secrets Manager Use Cases [Idira Success Blog] Design Recommendations for Idira Secrets Management: A Comprehensive Guide For Secrets Manager, Self-Hosted: Key tasks by role: [Idira Product Docs] Safe Manager adds and manages access to safes in PAM [Idira Product Docs] Safe Manager adds LOB user [Idira Product Docs] Secrets Manager admin adds and manages workloads [Idira Product Docs] Secrets Manager admin manages access to safes [Idira Product Docs] Developer defines workload identities For Secrets Manager, SaaS: [Idira Product Docs] Tutorial (steps 2-5) If you are following the Standalone path as opposed to a PAM-driven secrets management strategy, you will replace step 4 in the tutorial with these instructions. Key tasks by role: [Idira Product Docs] Safe Manager adds safe in PAM and syncs safe to Secrets Manager, SaaS [Idira Product Docs] Secrets Manager admin manages workload access to Secrets Manager [Idira Product Docs] Developer defines workload identities Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: >3 licensed workloads are utilized >3 secrets onboarded Stage 3: Secrets Availability Availability is key to maintaining operational continuity. You can leverage followers for the Self-Hosted infrastructure or edge nodes for SaaS to achieve resilient, scalable secrets delivery that meets uptime and performance requirements across regions and workloads. This stage focuses on: Ensuring high availability of secrets Building redundancy and failover mechanisms Avoiding bottlenecks or downtime that could disrupt workloads Resources For Secrets Manager, Self-Hosted: [Idira Product Docs] Set up followers For Secrets Manager, SaaS: [Idira Product Docs] Enable local access to Secrets Manager secrets with Edge nodes Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: For Secrets Manager, Self-Hosted: 100% of regions have followers deployed For Secrets Manager, SaaS: 100% of regions have edge nodes deployed Stage 4: Secrets Delivery Now that secrets are onboarded and only the appropriate workloads are allowed to fetch them, those workloads need to establish a secure connection to Secrets Manager. This involves: Integrating secrets delivery into CI/CD pipelines, automation tools, container orchestration platforms, or cloud services Using APIs, SDKs, or native integrations to inject secrets at runtime Ensuring delivery is encrypted and authenticated This step ensures secrets are delivered securely without hardcoding or manual handling, leveraging native and seamless integration mechanisms. Resources [GitHub repository] Accelerators [Idira Marketplace] Marketplace integrations for Secrets Manager For Secrets Manager, Self-Hosted: [Idira Product Docs] Secrets Manager, Self-Hosted integrations documentation Key tasks by role: [Idira Product Docs] Secrets Manager admin configures workload authentication [Idira Product Docs] Secrets Manager admin sets up authenticators [Idira Product Docs] Developer authenticates workloads [Idira Product Docs] Developer retrieves secrets For Secrets Manager, SaaS: [Idira Product Docs] Tutorial (steps 6-8) [Idira Product Docs] Secrets Manager, SaaS integrations documentation Key tasks by role: [Idira Product Docs] Secrets Manager admin configures workload authentication [Idira Product Docs] Developer sets up workloads to authenticate to Secrets Manager [Idira Product Docs] Developer sets up workloads to fetch secrets from Secrets Manager Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: Check for ongoing secrets retrieval activity: For Secrets Manager, Self-Hosted: Run activity report (filter on Retrievals) For Secrets Manager, SaaS: Run activity report (filter on Retrievals) Stage 5: Secrets & Workload Lifecycle Management The next level of Secrets Management maturity is to establish security-driven processes for onboarding and offboarding secrets and workloads. This includes defining rotation policies per platform and enabling automatic rotation to support secure operations across environments: Define a consistent workflow for requesting a new secret to be managed by Secrets Manager Rotate secrets regularly to reduce exposure Decommission secrets when workloads are retired Maintain an audit trail to demonstrate secrets management policies are properly enforced  Resources [Success Office Hours recording] Design a Machine Identity Security Program at Scale Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: >50% of licensed workloads are utilized >50% of secrets onboarded Average secrets age within SRS policy (if rotation applicable) Stage 6: Secrets & Workloads at Scale As your secrets management usage expands across the organization and workload types, the need to automate the lifecycle management process defined in the previous stage becomes crucial to enforce secrets management policies without becoming a bottleneck for DevOps, application, and cloud teams. This stage focuses on: Scaling secrets processes across hybrid environments Automating onboarding, rotation, and monitoring Managing secrets across containers, VMs, cloud services, and on-prem systems Enabling self-service onboarding of secrets  Resources [Success Office Hours Recording] Streamline Machine IAM with Self-Service Automation For Secrets Manager, Self-Hosted: [Idira Product Docs] Automate via REST API For Secrets Manager, SaaS: [Idira Product Docs] Automate via REST API Measuring Your Success Use the following metrics to assess whether you have successfully gained this capability: Ongoing REST API calls for lifecycle management activities   Stage 7: Secrets & Workload Intelligence The final stage is about turning data into insight. With secrets intelligence, you can: Analyze usage patterns to improve security posture Identify risky behaviors or misconfigurations Optimize secrets management based on real-world data This is where secrets management becomes proactive, not just reactive. Resources [Idira Product Docs] Audit logs and events For Secrets Manager, SaaS: [Idira Product Docs] View audit logs Measuring Your Success In Stage 4 of this Success Blog, we showed you how to check audit and activity reporting based on your Secrets Manager infrastructure. Those reports will continue to be useful for measuring the ongoing success with Secrets Manager as you scale up adoption. There is also a Resources page in the Secrets Manager, SaaS UI (example shown on this docs page) along with the Workloads UI page that will provide more insights into the full inventory of resources stored within Secrets Manager. The Secrets Manager, Self Hosted UI also has pages to view the various resources. Wrapping Up: Your Secrets Management Success Awaits CyberArk’s Secrets Manager Success Path isn’t just a roadmap—it’s a strategic framework for building a resilient, intelligent secrets management program. Whether you're just starting out or looking to mature your existing practices, each stage offers clear guidance and actionable steps. By following this path, your organization can reduce risk, improve operational efficiency, and stay ahead of evolving threats in the age of hybrid infrastructure and agentic AI. Ready to take the next step? Idira is here to guide you every step of the way. If you have questions, visit the Secrets Management Resource Center or contact your Idira Account Team.
View full article
Synchronizer's job is to push secrets from the Privileged Account Manager (PAM) Vault to the Conjur Vault. To perform its job, it stores some metadata concerning its last synchronization for each Line of Business (LOB) user. The next synchronization it run, it will compare this metadata with the metadata of the secrets to determine if the secrets need to be rotate.  Case 1 : - Last synchronization occurred 10min ago, secrets have been changed 3min ago -> The secret will be push into Conjur Case 2 : - Last synchronization occur 10min ago, secrets have been change 30min ago -> The secret should already be into Conjur and do not need to be push again.  This workflow is in place to optimize the way the synchronizer work.  However after restoring from a back up that can be a problem, and some secrets might be restore to previous version and will not be touch by the synchronizer before there next rotations.  This is one of the reason why you might want to force the resync of all the secrets in Conjur.  Steps To Force a full synchronization you need to perform the following : - Connect to the synchronizer server. - Stop the "Idira Vault-Conjur Synchronizer" service. - Move to that directory : C:\Windows\System32\config\systemprofile\AppData\Roaming\CyberArk\VaultConjurSynchronizer\metadata For versions below 13.0: C:\Windows\System32\config\systemprofile\AppData\Roaming\CyberArk\VaultConjurSynchronizer\ - Remove all the file named as follow : <LOBUser>.dat - Start the "Idira Vault-Conjur Synchronizer" service The <LOBUser>.dat contain the information of when the last synchronization occurs. By removing it, the synchronizer will consider it never synchronize the secrets of that LOBUser and will resynchronize all it secrets and create a new <LOBUser>.dat file.
View full article
This guide provides a comprehensive, step-by-step explanation of onboarding an AWS Organization (a collection of multiple AWS accounts managed together) into Idira Connect Cloud Environments (CCE). It includes an in-depth overview of AWS CloudFormation—what it is and what it does in this process—along with prerequisites, detailed procedures, security considerations, troubleshooting, and a full breakdown of the template. The process enables secure integration of your AWS environment with Idira services, allowing centralized management of privileged access, secrets, and entitlements without sharing permanent credentials.   What is AWS CloudFormation and What Does It Do?   AWS CloudFormation is a powerful Infrastructure as Code (IaC) service provided by Amazon Web Services. It allows you to define and provision AWS resources in a predictable, automated, and repeatable way using template files (written in JSON or YAML).   Think of it like a blueprint: You write (or download) a template that describes exactly what AWS resources should be created—such as IAM roles, policies, notification topics, or StackSets. What it does:   Automates deployment: Instead of manually creating resources in the AWS console, CloudFormation reads the template and builds everything for you. Manages stacks: A "stack" is the set of resources created from one template. CloudFormation can create, update, or delete entire stacks with one command. Supports multi-account deployments: Using StackSets, it can deploy the same resources across multiple AWS accounts and regions simultaneously—critical for AWS Organizations. Ensures consistency and safety: Templates include rules for validation, rollback on failure, and change management. In the context of Idira CCE onboarding:   Idira generates a customized CloudFormation template (a JSON file) based on your AWS Organization details and selected services. This template creates secure cross-account IAM roles (temporary access only), notification hooks (using SNS), and service-specific components (via StackSets). It establishes trust between your AWS environment and Idira using only temporary credentials from AWS STS — no permanent keys or static access ever shared. No manual resource creation is needed; everything is automated and auditable. Steps Important Prerequisites   Before starting:   Enable Trusted Access in AWS Organizations (done once in the management account): Log into the AWS management account console. Go to AWS Organizations > Services tab. Enable trusted access for "Identity and Access Management" and "CloudFormation". For IAM and CloudFormation (required for cross-account role creation and StackSets). Steps: This allows safe, organization-wide deployments.   Permissions Needed: In CyberArk: User with Cloud Onboarding role (often DpaAdmin or Secrets Hub Admin). In AWS: Admin access in the management account. Step-by-Step: Onboarding an AWS Organization in Idira CCE   1. Navigate in Idira Console Log into your Idira tenant. Go to: Administration > My environment > Cloud connectivity > Connect cloud environments > AWS environment. 2. Add the AWS Organization   Click Add > Add AWS Organization. Fill in Organization details:   Organization ID (starts with "o-"): Found in AWS Organizations dashboard. Root ID: Usually the same as Organization ID. Management Account ID: 12-digit ID of your primary account (top-right in AWS console > Account). Organization name (optional): Friendly name. Deployment region: Usually us-east-1 (matches your Idira tenant region).   Click Next. 3. Select and Configure Services   Choose services to enable (e.g., SIA, Secrets Hub). Review configurations (pre-filled where possible). Click Download CFT (CloudFormation Template) to get the JSON file. 4. Deploy the CloudFormation Template in AWS   Run this in the management account and correct region:   Open AWS Console > Search for CloudFormation. Create stack > With new resources. Upload the downloaded JSON template. Name the stack (e.g., "CyberArk-CCE-Onboarding"). Review parameters (mostly pre-filled by CyberArk). On review page: Acknowledge IAM resource creation. Create stack. What Happens During Deployment (5–20 minutes):   Validation rules check account ID and region. Creates cross-account IAM role for Idira (temporary access only, assumable via STS). Sets up SNS hooks for status notifications (start, scan, complete). Deploys service-specific resources via StackSets across all accounts. Sends verification messages back to CyberArk. Success Indicators:   Stack status: CREATE_COMPLETE in AWS CloudFormation. In CyberArk: Return to Administration > My environment > Cloud connectivity > Connect cloud environments > AWS environment. This opens the AWS environment page (the main dashboard for AWS connections).   Your connected AWS Organization appears as a row or card. Next to each service enabled (e.g., SIA, Secrets Hub), you'll see green checkmarks (or success icons) confirming successful deployment. The row also shows the number of accounts connected (total member accounts onboarded and synced). Overall status is "Active" or fully connected. 5. Troubleshooting Failures   Check CloudFormation Events tab for errors (e.g., trusted access not enabled, wrong region). Delete failed stack and retry after fixing. Common issues: Missing trusted access, incorrect IDs, permissions. In CyberArk, partial failures may show warnings like "Needs attention" instead of green checkmarks. Main Parts of the Template (Simple Breakdown) Full List of Main Resources from the JSON Template   Here is the complete list of the primary logical resource names as they appear in the "Resources" section of the generated CloudFormation JSON template (this template as shown is used for deploying both SIA and Secrets Hub in CCE):   CyberArkOnboardingCrossAccountRole OrganizationDeploymentStartedHook OrganizationScanHook OrganizationDeploymentCompleteHook dpaStack dpaStackSet secretshubStack secretshubStackSet Note on order in the JSON file: The actual order in which these resources are listed in the JSON template does not matter. CloudFormation does not create resources in the order they appear in the file. Instead, it automatically determines the correct creation order based on explicit dependencies (like the DependsOn attribute on the Complete hook) and implicit dependencies (e.g., a StackSet needing the cross-account role to exist first so Idira can assume it to deploy across accounts). This makes the template safer and less error-prone — you don’t have to manually manage the sequence. The CloudFormation template (a JSON file) has two big sections: Resources These are the actual things that get created in your AWS accounts. They are grouped below into logical categories, with a short explanation of what each group means, followed by the resources and their simple explanations: Core Security Component - Role Creation   What this group means: This is the single most important foundation for all security in the integration — the resource that creates the temporary IAM role allowing Idira to securely access your AWS environment without any permanent or static credentials. CyberArkOnboardingCrossAccountRole – The special IAM permission role (temporary by design) that allows Idira to safely access your AWS accounts using only short-lived credentials (no permanent keys shared). This resource is the one that creates the cross-account IAM role in your management account. Notification Hooks (Progress Messengers)   What does this group mean: These are automated messages sent back to Idira at key moments during deployment so your console always knows exactly what stage the onboarding is at. Each hook is a custom resource in CloudFormation. It uses a ServiceToken that points to an SNS topic owned by CyberArk. Simple example of a ServiceToken (one of the actual values from a generated template): "ServiceToken": "arn:aws:sns:us-east-1:871697792279:add-organization-org-complete-us-east-1" Why each hook has a ServiceToken: When CloudFormation creates the hook, it automatically sends a message to this SNS topic. Idira is listening to the topic and instantly receives the update — no direct connection or credentials needed from your side. What "Idira is listening to the topic" means (simple explanation) The SNS topic lives in CyberArk's own AWS account. When your deployment sends a message to it, Idira has a secure subscriber (like a small service) attached to the topic on their side. This subscriber receives the message almost instantly and relays it back to your specific Idira tenant (your company's private space in CyberArk). Idira then processes the message and updates your tenant's CCE console accordingly:   Successes: Shows progress, verifies resources, and displays green checkmarks when everything is complete. Failures: Detects issues (e.g., from errors in the payload or missing resources) and shows warnings or "failed deployment" status in your console. It's a safe, one-way notification: your account only sends, Idira only receives and relays the status directly to your tenant. Actual execution order of the hooks (the logical order in which they fire during deployment):   OrganizationDeploymentStartedHook Sends an immediate “we’re starting now” message to Idira so your console shows that onboarding has begun right away. Why first: This hook is created early (usually right after the cross-account role). It fires as soon as the basic setup begins, letting your CCE console immediately show "deployment in progress" — even before the heavy lifting (StackSets across accounts) starts. OrganizationScanHook Sends a detailed list of everything that was created (like resource IDs, ARNs, versions, regions) so Idira can double-check and verify it all. Why second: This runs after the service-specific StackSets (dpaStackSet and secretshubStackSet) finish deploying across all accounts. Idira needs the full inventory of what was built to perform its safety verification before activating features. OrganizationDeploymentCompleteHook Sends the final “all done successfully” message only after everything else is fully built, triggering the green checkmarks in your Idira console. Why last: This is explicitly the final step. It has a DependsOn attribute that forces CloudFormation to wait for all other key resources (including both StackSets and the Scan hook) to complete successfully. Only then does it send the "complete" message — ensuring no false positives and that green checkmarks only appear when everything is truly ready. This order guarantees smooth progress visibility, thorough verification, and reliable final confirmation — all while keeping the process secure and automated. SIA (Secure Infrastructure Access) Components   What this group means: These resources enable the Secure Infrastructure Access (SIA) feature — the just-in-time, temporary access to your AWS servers, databases, and other resources. dpaStack – Builds the central pieces needed for SIA in the management account only. dpaStackSet – Automatically copies and deploys those SIA pieces to every member account and selected regions in your AWS Organization. Secrets Hub Components   What this group means: These resources enable the Secrets Hub feature — centralized storage, rotation, and automatic synchronization of secrets with AWS Secrets Manager across your accounts. secretshubStack – Builds the central pieces needed for Secrets Hub in the management account only. secretshubStackSet – Automatically copies and deploys those Secrets Hub pieces to every member account and selected regions in your AWS Organization. Rules Section Runs first and checks two things:   The exact AWS account number matches what is expected. The geographic region (data center location, usually us-east-1) is correct. If either is wrong, the template stops immediately with a clear error — preventing accidental setup in test accounts, wrong regions, or member accounts.
View full article
Question How do I enable debugging and gather logs for the Central Credential Provider? Answer The procedure associated with raising debug levels for logging  for CCP ( Central Credential Provider)  consists of two parts, as below:  i. Enable debug  for CP ii. Enable debug  locally on the CCP server    Details for each part can be found as below -  i. Enable debug for CP a. For  'Privileged Cloud' aka pcloud deployments, use below linked KBA to perform this step - https://community.cyberark.com/s/article/Configure-Debugging-for-Privilege-Cloud-Connected-Credential-Providers  b. For Self-Hosted Vault deployments please do the following -  Use the 'PrivateArk Client' to open the 'AppProviderConf' safe and create a copy of the "main_appprovider.conf.[Platform].[Version]" stored in the root folder and call it _debug. For example, if you're using a Windows 9.7 provider, you would copy "main_appprovider.conf.Win64.9.70" to "main_appprovider_debug.conf.Win64.9.70". Open this new file and uncomment/set the following debug parameters:  [Debug]  CacheDebugLevels=0,1,2  AppProviderDebugLevels=0,1,2,3,4,5  ProtocolDebugLevels=0,1,2  ii. Enable debug locally on the CCP server  1. Edit the local 'basic_appprovider.conf' configuration file ("C:\Program Files\CyberArk\ApplicationPasswordProvider\basic_appprovider.conf" by default) by changing the 'AppProviderVaultParmsFile' parameter in the file, for example: AppProviderVaultParmsFile=main_appprovider_debug.conf.Win64.9.70   2. Enable debug for 'AIMWebService' a. For version 12.6 and later, please refer to documentation: https://docs.cyberark.com/credential-providers/Latest/en/Content/CCP/Configure_CCPWindows.htm In C:\inetpub\wwwroot\AIMWebService\web.config, find the following section  <log4net> .... <root> <level value="INFO"/> <appender-ref ref="RollingLogFileAppender"/> </root> </log4net> Change the value "INFO" to "ALL". b. For version 12.4 and earlier, follow the steps below: Open the file C:\inetpub\wwwroot\AIMWebService\web.config  Find the line:  <add name="AIMWebServiceTrace" value="0"/>  Set Value to 4 (verbose). Ensure the "logs" folder is created and has the appropriate permissions. This is a manual step that may have already been done on your install. Go to C:\inetpub\wwwroot\AIMWebService and create a new folder, called "logs"  .Right click the logs folder → Properties → Security → Edit  There should already be an inherited permission for the IIS_IUSRS group (name may be different depending on your app pool setup).  Check the boxes for Allow Modify and Allow Write for IIS_IUSRS.    IMPORTANT:  To make the configuration changes take effect do the following -  ** Restart the 'Idira Application Password Provider' Service. ** From an elevated command prompt, run "iisreset". Log Collection  Rerun the web call that failed, and then please upload the following to the case: a. 'Credential Provider' logs   \Program Files\CyberArk\ApplicationPasswordProvider\Logs: APPconsole.log APPtrace.log APPaudit.log b. AIMWebService Logs  \inetpub\wwwroot\AIMWebService\logs\AIMWSTrace.log c. IIS logs \inetpub\logs\LogFiles\W3SVC1' on CCP server(s)   d. Install Logs ( if the troubleshooting is related to Installation process) In the %TEMP% directory, there will be at least one folder that's a few random characters and then ".tmp", for example "VSDDA1F.tmp". In that directory should be an install.log for the CCP install. Example: C:\Users\<username>\AppData\Local\Temp\VSD51C7.tmp
View full article
We will update this article based on the questions we receive about the security bulletin. Please click the Follow button to receive change notifications    How can I check if my Vault and other components are compatible? Follow our documentation according to the target version * Credential Provider * Central Credential Provider * Application Server Credential Provider * z/OS Credential Provider   Where can I see the changes done in newer versions and patches? All release notes can be found Here
View full article
We will update this article based on the questions we receive about the security bulletin. Please click the Follow button to receive change notifications    How can I check if my Vault and other components are compatible? Follow our documentation according to the target version * Credential Provider * Central Credential Provider * Application Server Credential Provider * z/OS Credential Provider   Where can I see the changes done in newer versions and patches? All release notes can be found Here
View full article
On Wednesday, May 13, 2026 we disclosed several vulnerabilities affecting the Secrets Management products. As the product line is in transition to the Palo Alto Networks’ Network Security platform, the disclosure has been performed under that platform’s standard. Please see https://www.cyberark.com/ca26-20 for the disclosure details. We will update this article based on the questions we receive about the security bulletin. Please click the Follow button to receive change notifications Are there any pre-upgrading steps that should be carried out before upgrading? Backup your current environment Verify the minimum requirements for Conjur Enterprise and Vault Synchronizer Review the deployment workflow to ensure the usage of the relevant commands needed What are the steps needed to upgrade Conjur Enterprise? Follow the steps described on our online documentation What happens if the iss (issuer) claim is missing in the JWT? If the JWT Authenticator is configured with an issuer setting and the JWT presented does not include the iss claim, authentication will fail. This is by design to enforce strict validation Where can I find the Release Notes and fixed bugs for each release: Release notes can be found on our online documentation A link to each version's fixed bugs list can be found at the "Bug fixes" of each version When can I find Conjur OSS documentation? Conjur OSS documentation can be found here  
View full article
ASCP Introduction The Application Server Credential Provider is a tool that provides Java Enterprise Edition Server (J2E) Passwords. J2E servers provide a framework to developers that allow them to build small applications without having to build out entire parts of an application architecture on their own. One of these components are Datasource's which allow developers to reach out to databases and other types of directories with simple API calls. These Datasources require passwords to authenticate to their databases. This is where the ASCP comes in. Instead of storing the password somewhere in the J2E server, the ASCP calls the provider Java SDK for passwords when a new connection in needed.   Steps Common Issues The top issue with the ASCP is initial configuration issues followed by performance issues.   When the ASCP has a configuration issue it will stop the ASCP from either being loaded or called.  When this happens you usually do not get additional logs in the J2E server, the provider, or the Vault. The reason for this is that the ASCP is technically its own application that is running in the J2E server. Like any application that fails to run you may not see that applications specific logs until the app started. For these issues it is critical to document and confirm configuration steps taken. When opening an ASCP case the support team will be looking for the following: List of files copied into the J2E server structure and to which directories Screenshots of GUI based configruation XML configuration files (Most GUI J2E server still store their configurations in XML) ASCP Specifc Trace logging Since the ASCP is its own application it can create its own log entries. Each ASCP type has its own tracing configuration and their logs usually go into the J2E servers main log unless their server admins have changed default logging ASCP logging configuration can be found in each separate products section in the online documentation: https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/admin_ASCP.htm Once the ASCP logs have been enabled (or trying to confirm if the ASCP jar is loading at all) looking for common key words like cyber (the product name shows up in the log entry) credmapper, and the version number can help to find ASCP general events. The first major event is to see if the ASCP jar file is loaded. the next event to look for is calls from the ASCP to the provider. Failed called will generally appear but successful calls will need tracing enabled. This is where ASCP issue types will divide, configuration issues will usually need permissions or provider query to be updated. For performance issues calls most likely all successful but number of calls per minute is what developers and admins would want to see. Generally Available ASCP types   J2E Server Cred Mapper JDBC Driver Proxy JBoss Yes Yes Weblogic Yes Yes Websphere Yes No Tomcat No Yes The JBOSS and Weblogic JDBC Driver Proxy ASCP's are more recently released. They have have better performance and compatibility compared to their older credential mapper ASCP's but at the risk of losing security controls. The credmapper model allows for deployment level application authentication while the driver proxy essentially trusts any deployment on the J2E server. Please refer to the online documentation for a more detailed breakdown on the differences between ASCP's https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/admin_ASCP.htm  
View full article
Question How does the Application Password provider determine the IP address of the system where the application runs (its own IP address)? Why does my Application Provider for UNIX / Linux see the application running from IP Address 127.0.0.1? Answer The provider uses OS system calls to lookup IP address of the system using its internal name. On Linux/Unix systems name can be found by executing uname -a command. On Windows machines name is defined in computer properties. (Right click on My Computer > Properties > Computer Name) Most likely it is because the server name is mapped to 127.0.0.1 in /etc/hosts file. In order to correct this, remove the mapping from /etc/hosts file and re-install Application Password Provider on the server. Q: How does the Application Password provider determine the IP address of the system where the application runs (its own IP address)? A:  The provider uses OS system calls to lookup IP address of the system using its internal name. On Linux/Unix systems name can be found by executing uname -a command. On Windows machines name is defined in computer properties. (Right click on My Computer -> Properties -> Comuter Name) Q: Why does my Application Provider for UNIX / Linux see the application running from IP Address 127.0.0.1? A: Most likely it is because the server name is mapped to 127.0.0.1 in /etc/hosts file. In order to correct this, remove the mapping from /etc/hosts file and re-install Application Password Provider on the server.
View full article
The below PowerShell scripts shows examples of how the CCP can be called using a client certificate for authentication. These scripts are provided on example basis only, and assume SSL verification is successful between the client and the CCP server.   CCP API Request example (this is the format expected in the first two scripts below): https://ccp.cybr.com/AIMWebService/api/Accounts?appid=sampleapp&safe=demosafe&address=1.1.1.1   Steps For use with .cer certificate file: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $URI = "CCP API request" $cert = "Absolute path of .cer file" $res = (Invoke-RestMethod -Method Get -Uri $URI -Certificate $cert) echo $res   For use with .pfx certificate file: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $URI = "CCP API request" $certPath = "Absolute path of .pfx file" $cert = Get-PfxCertificate -FilePath $certPath $res = (Invoke-RestMethod -Method Get -Uri $URI -Certificate $cert) echo $res For use with a certificate in the Windows Certificate Store: See attached Powershell script file.
View full article
We will update this article based on the questions we receive about the security bulletin. Please click the Follow button to receive change notifications. I want CyberArk to upgrade my environment, what should I do? PAM and EPM Self-Hosted customers can fill up a Service Request form in the Technical Community Privilege Cloud customers can contact their account manager How can I check if my Vault and other components are compatible? Follow our documentation according to the target version * Credential Provider * Central Credential Provider * Application Server Credential Provider * z/OS Credential Provider   Where can I see the changes done in newer versions and patches? All release notes can be found Here
View full article
For Conjur 13.0+ versions, there are four Postgresql settings that should be changed when increasing the supported Standby and Follower count from the default of 16 Steps These are: ===== - 'max_wal_senders': Default is 16. This should equal the maximum number of Standbys and Followers planned in the Conjur deployment. - `max_connections`: Default is 100. This should increase by 2 for each additional Follower planned about the default. For example, if the `max_wal_senders` is increased to 20, then `max_connections` should be at least 108. - `max_worker_processes`: Default is 26. This should be at least 10 more than the max_wal_senders value. For example, for 20 wal senders, the max worker processes should be at least 30. - `max_replication_slots`: Default is 21. This should be at least 5 more than the max_wal_senders value. For example, for 20 wal senders, the max replication slots should be at least 25 ===== ------------------------------------------------------------------------------------------------------------------------------------------------------------------ For versions prior to 13.0, there are only two parameters to configure per your needs: "max_connections" and "max_wal_senders" The process for managing them is here: Changing the "max_connections" and "max_wal_senders" for DAP containers
View full article
Question What happens to the cache encryption mechanism when you upgrade to Credential Providers v12.1? Answer The cache encryption mechanism has been upgraded. If your Credential Provider uses cache, it will be re-encrypted automatically using the new cache mechanism after upgrading to Credential Providers v12.1.
View full article
Question How is OS User authentication different between the local credential provider and the Central Credential Provider web service? Answer The CCP uses a different mechanism than the local provider to capture the OS user. The difference has more requirements and more limited use cases. On the local provider when using OS user as an application authentication restriction the provider uses the process ID of the calling application to look up which user started the process in the process table. At a high level this is the same process for local providers on both Windows and *Nix variants. On the CCP OS user is captured using an IIS function known as Windows authentication. On a human interactable web site when opening a new session Windows Authentication will bring the end user to their desired page hosted on IIS without being prompted for a username and password. The way this works is that when the end user accesses an Windows Authentication protected website their local authentication token is passed to IIS which then verifies the token is valid with Active Directory. Windows Authentication has more requirements: The system making the call to the CCP must be on the same domain as the CCP server The user whose name is specified as OS User must have a domain session on the host they are making the call from. The call must come from this session. The method/language making the call to the CPP must support passing the authentication token. Anonymous Authentication may need to be disabled. (this will restrict the CCP application to only allow Windows Authentication calls) In power shell and .Net the “UseDefaultCredentials” property will send the users authentication token when making a REST call. An example rest call in PowerShell that will forward the session token of the user executing the command   invoke-webrequest -method GET -UseDefaultCredentials -ContentType application/json -uri https://pvwa.taco.day/AIMWebService/api/Accounts?AppID=dave"&"username=bear  
View full article
  • 79 Posts
  • 7 Subscriptions