I'm trying to manage a Linux host from One Identity via the Powershell connector (the Unix connector doesn't have the features we need and support said their is no way to change that, thus powershell). I've created my definition file and setup the connector. The definition file has a custom cmdlet in it that establishes an SSH connection to the Linux host (Ubuntu Server 18.04.1), runs a script, and gathers the returned data. I've placed logging elements throughout the Powershell and Bash scripts, and I can confirm that the SSH tunnel is created, the script is executed on the Linux host, and the expected data is returned to the job server running the synchronization editor. However, while simulating a data pull from the Linux host into One Identity, Synchronization Editor hangs up and must be killed with Task Manager.
I've set the connector to log every possible item in both directions, and the workflows are set to break on error, yet the Synchronization Editor hangs up upon the data being returned. Not only is it falling to break on error, but it is also not generating log files of any kind. Has anyone else had a similar experience? I've opened a support case, but I was curious if I there are others out there who have been down this road. How can I troubleshoot this further if there are no log files generated and the Sync Editor workflows are not breaking on error? I've check the Event Viewer on the server, but the only relevant record in there is for the face the process has hung and doesn't provide any further detail as to why.
- Products
- Solutions
- Resources
- Trials
- Support
- Partners
- Communities