AutoIT - Self Hosted vs Privileged Cloud

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

AutoIT - Self Hosted vs Privileged Cloud

L3 Networker

Dear Community,

we have a custom Connection Component (AutoIT) to open the Active Directory snap-in (dsa.msc). It works in our On-Prem environment, but it does not work in Privilege Cloud.

Could you tell us if a Connection Component in P-Cloud requires a different configuration?

On the PSM server (from which we want to route the connection to the AD snap-in) are there any special settings needed? RSAT tools enabled. and from the system itself we can open dsa.msc manually without issues).

Do we need to adapt the AutoIT script?

 

In Privilege Cloud we can see the connector selectable, but when we click PSM Connect, the RDP session closes unexpectedly before showing the AD snap-in.

 

Configuration details:

- In Configuration Options we set the ClientDispatcher under Target Settings.

- The component is enabled in Platform Management for the related platform.

- On the PSM server AutoIT is installed, and the dispatcher configuration points to:

ClientDispatcher C:\Program Files (x86)\AutoIt3\AutoIt3.exe "{PSMComponentsFolder}\PSM-ADUtenti&GruppiADDispatcher.au3""{PSMComponentsFolder}" 

 

Additionally:

Is there a way to extract from Reports or Monitoring which Connection Components are actually being used, so we can migrate/test only the relevant ones in P-Cloud and exclude old/unused components?

Thank you very much

1 accepted solution

Accepted Solutions

L6 Presenter

There isn't anything specific to be changed for connectors going from Self-Hosted to Privilege Cloud. The PSM and connector behaviour remains the same.

 

You can check the following:

  • Connection component configuration in the Privilege Cloud portal matches that of what you had in the functional Self-Hosted setup
  • The paths the connection component is pointing to to execute the scripts is correct, that is, the executables with that name are present in the folder
  • AppLocker configuration - Ensure you've whitelisted everything you need to to get this connection component working. Validate that it's not an AppLocker issue by turning off AppLocker (Audit Only) and rerun the session. If it works, enable AppLocker and run the session again. Then check Event Viewer logs -> Windows Logs -> Application and Services Logs -> Microsoft -> AppLocker. Check for any blocks displayed in this section
  • If the steps above don't fix it, enable full PSM debugging and check PSM trace and component logs

 

I'm not entirely sure if there's a better and more reliable way to get reporting on connector usage, but you could generate an Activity Log report from the Privilege Cloud portal and focus on the audit codes 300 (PSM Connect) and 301 (PSM Connect Failed). In the report sheet, check the 'New Target' column, that should show you the connection components in use. I'd wait for the other community members to weigh in as well though!

View solution in original post

6 REPLIES 6

L6 Presenter

There isn't anything specific to be changed for connectors going from Self-Hosted to Privilege Cloud. The PSM and connector behaviour remains the same.

 

You can check the following:

  • Connection component configuration in the Privilege Cloud portal matches that of what you had in the functional Self-Hosted setup
  • The paths the connection component is pointing to to execute the scripts is correct, that is, the executables with that name are present in the folder
  • AppLocker configuration - Ensure you've whitelisted everything you need to to get this connection component working. Validate that it's not an AppLocker issue by turning off AppLocker (Audit Only) and rerun the session. If it works, enable AppLocker and run the session again. Then check Event Viewer logs -> Windows Logs -> Application and Services Logs -> Microsoft -> AppLocker. Check for any blocks displayed in this section
  • If the steps above don't fix it, enable full PSM debugging and check PSM trace and component logs

 

I'm not entirely sure if there's a better and more reliable way to get reporting on connector usage, but you could generate an Activity Log report from the Privilege Cloud portal and focus on the audit codes 300 (PSM Connect) and 301 (PSM Connect Failed). In the report sheet, check the 'New Target' column, that should show you the connection components in use. I'd wait for the other community members to weigh in as well though!

L4 Transporter

@Marco Cipriano​ , I would suggest you to use the connector from marketplace https://community.cyberark.com/marketplace/s/#a352J000000GWAZQA4-a392J000002tNgLQAU and install it using Pcloud tools - Add PSMapps

https://community.cyberark.com/marketplace/s/#a352J000000GWAZQA4-a392J000002tNgLQAU

 

its easy to deploy and maintain.

L4 Transporter

@Marco Cipriano​ , I would suggest you to use the connector from marketplace https://community.cyberark.com/marketplace/s/#a352J000000GWAZQA4-a392J000002tNgLQAU and install it using Pcloud tools - Add PSMapps

https://community.cyberark.com/marketplace/s/#a352J000000GWAZQA4-a392J000002tNgLQAU

 

its easy to deploy and maintain.

L3 Networker

Thanks guys! One last thing, how can I find out which Connect Components are currently being used? The "Monitoring" section doesn't show anything.

L4 Transporter

Hello @Marco Cipriano​ 

 

You can find currently used connection components from PSM logs.

There is a community thread for configure PSM logs.

How do I turn on the PSM debug levels? Thank you

L4 Transporter

Hello @Marco Cipriano​ 

 

You can find currently used connection components from PSM logs.

There is a community thread for configure PSM logs.

How do I turn on the PSM debug levels? Thank you

  • 1 accepted solution
  • 214 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!