I just now confirmed that it still works in EG 7.15. I used the following steps:
-Created an EG project with a single program with the code "proc print; data=sashelp.class; run;", saved it, and then scheduled it (File->Schedule Project), so an EGScript1.vbs file would get created.
-Closed EG.
-Ran the VBScript file with the following command (since I'm using 32-bit EG):
c:\Users\cassmi\OneDrive - SAS\Desktop>c:\Windows\SysWOW64\cscript.exe EGScript1.vbs
-Confirmed that it runs properly (by re-opening the EG project and confirming that ODS results were created). (Note: This was with workspace server credentials stored in metadata, so not prompted.)
-In Server Manager plug-in in SAS Management Console, changed SASApp->SASApp - Logical Workspace Server, Properties, Options tab, Authentication service setting from "Host" to "Prompt".
-Manually connected to the SASApp server in EG, confirming that I am now prompted for credentials each time.
-Closed EG and then re-ran the VBScript file with the same command above.
-Confirmed that it no longer automatically runs successfully. Instead, now the credentials prompt is displayed. If you enter valid credentials it will then run successfully. If you do not enter valid credentials, it won't be able to connect to the workspace server, thus won't run. (You could make an argument that the credentials prompt shouldn't even appear (rather, just fail), since scripting/scheduling is intended to be non-interactive.)
-Created a credentials.xml file with the following contents and saved it to %appdata%\SAS\SharedSettings\7.1\credentials.xml:
<?xml version="1.0"?>
<xml FileVersion="7.1">
<credentials>
<server name="SASApp" userid="cassmi" password="yourPassword"/>
</credentials>
</xml>
-Closed EG and then re-ran the VBScript file with the same command above.
-Confirmed that it runs successfully again (without prompting for credentials, since they are now being picked up from the credentials.xml file).
I also confirmed that if I provide incorrect credentials in the credentials.xml file, then EG still writes out a credentials.failed.xml file in the same location.
Casey
... View more