05-06-2020, 04:11 PM
(05-11-2016, 12:04 AM)kgouldsk Wrote:(04-11-2016, 03:11 PM)DevOma Wrote: Did you try to use "ext app variables" - you can use a lot of data of your connection and assigned creds to call an ext app with parameters - just have a look into the help file - I think most of your issues should be not really a problem
Ext App can be "tried" to integrate as tab - but it depends on the app if this is working or not - you can try - but in you case it might be better to define your ext app once, configure your connections and run the ext app with the connection info...
Of course - that was the point of my indication that an Ext App is probably the easier way to go, but with an ext app, we need to have a command to call which will do the job, which was quite specifically my question. The Ext App has the variable support needed to do this - I've even given an example of the variable we need to use - (variable support isn't in the regular connection object - feature request!). But I need to be able to either call ASG-RD itself to add a tab, or call something like mstsc.exe and integrate - I don't think this is possible as we need to dynamically insert the command string into a temporary config file using a script, then feed that to mstsc which would launch, and would break the context of ASG-RD trying to capture the windows to insert it in a tab.
Does anyone have a demonstrated method for doing anything similar?
I bet you managed to solve the problem with parameterizing the alternate shell for use in CyberArk since the time it was reported. Can you share the receipe please?