AIM - How to enable debugging for the Application Password Provider

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Secrets Management Articles
3 min read
L0 Member
No ratings
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. 
  1. 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) 
     
  2. 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. 
  1. 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) 
     
  2. 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
Rate this article: