AutoIT/web_generic-v3.6

News since 3.5:

• wd.conf file in the same folder as the web_generic executable allowing the configuration of web driver, for example:
  -- kiosk mode, or any other browser behavior through the capabilities configuration (see commented / intact settings in wd.conf)
  -- skip the webdriver au3 code version check calling out to the Internet (needed change in wd_core.au3)
• Enhanced logging
• Disable _WD_IsLatestRelease, a callout to the Internet in wd_core.au3

AutoIT/web_generic-v3.5

Support for basic authentication.

If 'basicauth' is given after the targetUrl then no orchestration is performed, the browser is just navigating to what is given in --args.
In such case the targetURL may be given in the following format: {username}:{password}@{Target.AssetNetworkAddress}/optionalPage

Example (Active Roles Web Admin where there is an unmanaged Asset created for ARWebAdmin with type=Other):
--cmd "C:\AutoIT\wg\web_generic_3.5.exe" --args "1 c {username}@{Target.AccountDomainName}:{password}@{Target.AssetNetworkAddress}/ARWebAdmin basicauth" --enable-debug

AutoIT/web_generic-v3.4

Fifth command line argument for {asset} is optional now as {username} {password} {asset} are not all mandatory and does not need to be in this order from RemoteAppLauncher 2.0.0. This allows support for AWS.

AutoIT/web_generic-v3.3

ONLY FOR DEMO USE

cmd line arguments for launcher: OI-SG-RemoteApp-Launcher.exe --cmd \web_generic.exe --args "<debug=0|1> <firefox|f|chrome|c|edge|e> targetUrl v::css1::{username}||c::css2||c::css3||s::css4::{password}||o::css4::{Target.TotpCodes}::5||c::css5 {asset}"

Although the code supports Firefox (needs geckodriver.exe) and Edge (needs msedgedriver.exe) too:

• Edge has not been tested at all
• It is not reliable with Firefox. Also, it should disable devtools but in the tests not all of them got disabled and users can re-enable them at this point.

Web orchestration parameters:
The code supports any number of selectors, types of:

• "v" as value
• "c" as click
• "s" as secret which is not logged
• "o" as TOTP json input, with the minimum number of seconds required to enter the OTP before it expires. If the actual code is closer to expiry than the defined minimum seconds then the process is waiting the defined minimum seconds for the next code. If the actual code has already expired it just checks the next code. (requires SPP 7.2+ and RemoteApp Launcher 2.0.0+

separated by "||".

The actual action is defined with "::" separator.
Sample for Azure (with clicking No at the end when it asks "Stay signed in?"):
--cmd "C:\AutoIT\wg\web_generic_3.3.exe" --args "0 c portal.azure.com v::#i0116::{username}||c::#idSIButton9||s::#i0118::{password}||c::#idSIButton9||o::#idTxtBx_SAOTCC_OTC::{Target.TotpCodes}::3||c::#idSubmit_SAOTCC_Continue||c::#idBtn_Back {asset}"

Note: With passing the TOTP code to the application and the required additional actions, the full length of the RDP app input parameter may become longer than the maximum length allowed by MS Windows. You may put the exe in a different folder or just set the PATH environment variable and apply --use-path as described in the SPS admin guide. The code now accepts the first letter of the browser types for the same reason.

The code disables user input when not running in debug mode

AutoIT/sqlstudio_v2

New features:

• Support for connecting to SQL Server via SPS MSSQL proxy (inband destination selection) from the RDS host
• Support for defining SQL Studio installation folder via RemoteApp parameter (via environment variable which must be set first on the RDS host)
• Some logging added

Safeguard Launcher Application Command Line parameters: --cmd \sqlstudio.exe --args 0|1 {username} {password} {asset} [sps ip]
Tested with SSMS v18.4: --cmd "\sqlstudio.exe" --args 1 ssmsfolder {username} {password} {asset} 192.168.1.1
Test with direct connection to database: --cmd "\sqlstudio.exe" --args 1 ssmsfolder {username} {password} {asset}
Make sure you configure the environment variable on the RDS host, for example C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE

AutoIT/web_generic-v3.2

Altough the code supports Firefox (needs geckodriver.exe) and Edge (needs msedgedriver.exe) too:

• Edge has not been tested at all
• It is not reliable with Firefox. Also, it should disable devtools but in the tests not all of them got disabled and users can re-enable them at this point.

The code supports any number of selectors, types of "v" as value or "c" as click or "s" as secret which is not logged, separated by "||".
The actual action is defined with "::" separator.
Format: "v::css1::username||c::css2||c::css3||s::css4::password||c::css4"

--args sample for Azure portal login:
"1 chrome portal.azure.com v::#i0116::{username}||c::#idSIButton9||s::#i0118::{password}||c::#idSIButton9||c::#idBtn_Back {asset}"

User input is disabled for the period of the login workflow

AutoIT/web_Okta

Password Injection implemented based on XPath
User input is enabled once the password verify button is clicked

cmd line arguments for launcher: OI-SG-RemoteApp-Launcher.exe --cmd \web_Okta.exe --args "<debug=0|1> browser:chrome|firefox {username} {password} {asset}"

When using Firefox, devtools are disabled in preferences (although the user can re-enable them) at this point.

AutoIT/sqlstudio

Added AWS to apps.csv

AutoIT/web_generic-v2.0

This version is used by the samples in apps.csv of the OI-SG-RemoteApp-Publisher helper script.
Supports now two types of web applications:

• Username and password fields are shown on the same page
• A click is required after entering the username to get the password field shown.
  Debug logging is available.
  Chromedriver got updated to version 101.0.4951.41