- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
07-12-2019 06:24 AM
Scenario 1) When snow team member changes the credential ID to some wrong value, the audit give failure message and the IP doesn’t scan.
Scenario 2) But when Application team member, set the credential ID to correct one as before and scan the IP, the audit log of mid server shows "successfully fetched the password" but still the IP doesn’t discover.
Scenario 3) When they disable the credential ID and uses USERNAME AND PASSWORD, the IP scans successfully. It doesn’t create any log in Audit log file which is as expected.
In point 2, if the mid server uses the credential ID and hit the cyber ARK and fetch the password but doesn’t scan IP. Can you suggest what can be the problem?
07-13-2019 10:54 AM
in this case, I would ask SN admin to check MID discovery logs to identify the issue. It seems to me that you don't have any problem between the AIM agent and the vault. As long as you can cconfirms retrieval of the password, the issue is typically on the SN side, and need to make sure SN admins configure the discovery settings properly. A call with SN support may help. I did that quite often during the beginning of the integration.
07-14-2019 09:31 PM
thank you for your response.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

