How troubleshoot general ASCP issues

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Secrets Management Articles
3 min read
L1 Bithead
No ratings
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/...

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 ServerCred MapperJDBC Driver Proxy
JBossYesYes
WeblogicYesYes
WebsphereYesNo
TomcatNoYes

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/...
 
Rate this article:
  • 2403 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-13-2025 09:01 PM
Updated by: