- 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.
09-14-2022 02:00 AM
Hi Folks,
We've a request from the customer to have some changes in the 'PSMRemoteMachine' drop down when the relevant PSM connection component is selected.
Currently, when an user selects the PSM connection component from the 'Connect' drop down, it then displays the 'Remote Connection Details' (added through 'PSMRemoteMachine' parameter in the connection component), where user can either type the hostname of the target server/ application manually or he can select it from the pre-defined list added through 'Limit Domain Access To' parameter.
Problem with this current option is, the pre-defined server list we already added shows all the Target Server/ Application hostnames irrespective of the connection component selected. This is causing confusion to the end users when all the Target Server/ Application hostnames is displayed at the same time irrespective of the connection component being selected.
Instead, customer is looking to see if is there any further customization that can be done in the PVWA interface, so that once the connection component is selected, only the relevant target hostnames are displayed to the end user to pick from the pre-configured list.
For example, if an user selects the connection component (PSM-RDP), only the Windows target hosts must be displayed to the end user in the further drop down (PSMRemoteMachine). Similarly, if an user selects some other web based connection component (PSM-Web), only the pre-configured web-URL's must be displayed to the user. Having this would be more helpful for teams who have long list of Target Hosts and URL's to pick from the pre-configured drop down.
Please share your thoughts or inputs on this, thanks.
Cheers,
Naren
09-14-2022 02:21 AM
I worked around this limitation by having customers add the account multiple times.
All 3 accounts are created in the same safe and are then grouped in an account group. Whenever a password change is triggered or scheduled for the group, the user's password will be change in the domain, and the same password replicated to the other 2 accounts.
Since the connect history (and target server list) is per-account, each account (and therefore each group of PSM CCs) will have its own list.
09-14-2022 02:36 AM
@Bernhard Brückler Thanks a lot for sharing your inputs on this
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!

