- 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.
12-13-2021 10:27 PM
Below are the details:
12-14-2021 02:43 AM
There can be couple of solutions.
12-14-2021 02:56 AM
You could create a new Vault group and give that permissions on the safe where your app's secret are stored, but then you would still need to automate the "add Prov_<NEW> user to that group" part.
12-14-2021 08:26 AM
The challenge here is whenever a new provider user is created on a new server, it's username is unknown and even if I have to automate its addition to the safe, I would first need to know it's name. The new provider username can be extracted from system health or from newly built application server where the AAM agent is installed.
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!

