Does your classpath include the SAS/SECURE JAR files (sas.rutil.jar sas.rutil.nls.jar sastpj.rutil.jar) ... View more

SAS allows you to prevent the email access method from being used at all using LOCKDOWN as Carl mentions. I think to limit what addresses can be used as the sender would be something done on the mail server you are using. ... View more

Does changing the argument for your jobRequest "_OMITSESSIONRESULTS" to "false" change the behavior back to providing _webout? ... View more

Yes, the same is true of WORK. ... View more

The Deployment Operator calls ses.sas.download to pull the cadence release file when deploying. If you have modified this to use an internal repository warehouse (not a mirror registry) you would need to update the files in your repository warehouse for the new version you are trying to deploy. These would have been pulled down when you run mirrormgr. ... View more

The message seems to be saying it can't find that specific release number when checking the repository warehouse. Are you supplying that release when building the deployment custom resource? Are you using an internal repository warehouse? ... View more

How are you performing the update? Where do you see that message? ... View more

You may want to take a look at this documentation on the configuration of the path lists for CAS, it sounds like you need to add this path as allowed or remove it from denied. Manage Path Lists (Allowlists and Denylists) https://go.documentation.sas.com/doc/en/calcdc/3.5/calserverscas/n03001viyaservers000000admin.htm#n03026viyaservers000000admin ... View more

The rejection seems to be coming from the application gateway, based on your description I'm guessing you're running against a size limitation in the configuration of the gateway. Here's some doc I found on Microsoft's site that might apply. https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-waf-request-size-limits ... View more

When upgrading you'd need to run mirrormgr again to mirror the images you'd also want to put the new repository warehouse files into the location served by your HTTP server. ... View more

Yes, I think the only caveat I'd point out is the contents of rel and lod are going to change when you pull a new release. ... View more

1. You are correct, the deployment operator pulls information from a remote location to get details on the deployment. 2. The documentation only covers the options (e.g. --repository-warehouse-location) and how to build the warehouse (mirrormgr doc for a air-gapped site) and not how to deploy an HTTP server to serve up this information. 3. Yes 4. No, we do not currently document how to set up a web server to serve up those files. ... View more