I found out how to turn on the option to have Studio allow you to use HTTPS to connect to the remote repository.  I am now able to connect to the remote repository.   FYI - You have to edit:  C:\Program Files\SASHome\SASStudio<studio_type>\<version>\war\config.properties <studio_type>: SingleUser, Basic, Enterprise*       (* Enterprise value not verified) <version>: SAS Studio version number (example: 3.81) Set webdms.showGitPassword=true Restart Studio Server Then you will have an option when creating a Git Profile to use HTTPS ... View more

Question: How would I add additional workers after the initial deployment?   Answer: Add them to the CAS worker group in inventory.ini and re-execute the site.yml playbook   Thanks to SAS Technical Support for the answer.   Scott ... View more

@SDV,   As we discussed yesterday, Kerberos authentication isn't supported for the CAS user when you starting the CAS server. You have to use passwordless SSH based on a keys authentication.   ... View more

With a little help from our friends at SAS Technical Support I was able to get the certificate imported.  Here are the instructions I was given that allowed me to successfully perform the import:   Edit the trustedcerts.pem file Copy the two certificates that are labelled as 'SAS VIYA Root CA' & 'SAS VIYA Intermediate CA' Copy just the two blocks like this, no comments, in the new file               -----BEGIN CERTIFICATE-----              <block of base-64 encoded text>              -----END CERTIFICATE-----              -----BEGIN CERTIFICATE-----              <block of base-64 encoded text>              -----END CERTIFICATE----- Paste the two certificates into a new file and save as a .pem file   As stated in the SDM panel's text about subject-issuer order with the root cert last, you need the intermediate cert block first, then the root cert block last. Run the SAS Deployment Manager to import the certificate from the new .pem file Now, off to create the authinfo file... ... View more

Webwork needs to be set to a location that is shared to each grid node when using grid launched workspace servers.   Just FYI, here is some more information on webwork.   It is the default library when using Studio's interactive mode.  In interactive mode, each program gets a workspace server session, and all of the workspace server sessions from your Studio session share the webwork.  In a SAS grid when using grid launched workspace server sessions the workspace sessions can run on any of the grid nodes, therefore the directory used for webwork needs to be in a shared location accessible from each grid node.   See this blog entry for further information:  http://blogs.sas.com/content/sgf/2016/09/21/sas-st udio-tips-for-sas-grid-manager-administrators-wher ...  ... View more

... and the answer is ...   Yes.  Webwork needs to be set to a location that is shared to each grid node when using grid launched workspace servers.   Just FYI, here is some more information on webwork.   It is the default library when using Studio's interactive mode.  In interactive mode, each program gets a workspace server session, and all of the workspace server sessions from your Studio session share the webwork.   See this blog entry for further information:  http://blogs.sas.com/content/sgf/2016/09/21/sas-studio-tips-for-sas-grid-manager-administrators-where-are-my-preferences/    ... View more