Developers

FrankPoppe · Posted 10-16-2023 10:02 AM

I have a StoredProcess web application that relies on the Bootstrap and jQuery packages for layout and scripting.
The content is created through a series of DATA STEP's and PROC STREAM-calls, writing to _webout.
I have in the <head> section references to the Bootstrap and jQuery sources on their webpages. This used to work.
Increasingly however modern browsers refuse to load them because Content-Security-Policy directives block that.
The SAS web application generates HTTP-headers specifying so.

I have tried two ways to overcome that:

<meta http-equiv="Content-Security-Policy" content="...." /> in the <head> section
old = stpsrv_header("Content-Security-Policy" , "..." ) ;in a DATA STEP before opening _webout.

But the SAS-generated HTTP-header remains in force.

Any ideas?
(Except downloading the Bootstrap and jQuery packages and installing them locally in Config\Lev1\Web\WebServer\htdocs - I would like to avoid changes there)

AllanBowe · Posted 10-16-2023 10:46 AM

The option you describe (putting the web content on the web server) is in fact, the correct approach to take. Mixing HTML/CSS/JS/IMG/ICO/WOFF etc into DATA STEP and PROC STREAM is a very hacky / hard to maintain & extend way to build (non trivial) web apps.

The option you are probably looking for, would be to modify the CSP policy in the web server directly. You cannot change CSP policy from SAS code, nor from the content (or headers) of the WEBOUT destination.

More info here: https://sasjs.io/security/#content-security-policy

/Allan
SAS Challenges - SASensei
MacroCore library for app developers
SAS networking events (BeLux, Germany, UK&I)
Data Workflows, Data Contracts, Data Lineage, Drag & drop excel EUCs to SAS 9 & Viya - Data Controller
DevOps and AppDev on SAS 9 / Viya / Base SAS - SASjs

FrankPoppe · Posted 10-16-2023 11:04 AM

I agree in principle that using DATA STEP and PROC STREAM is a kind of a hack.
On my development system I have access to the sas.conf file, and to the .../htdocs folder. But the idea behind this application is that it can be imported and set up by SAS developers, and in a production system they usually do not have access to those locations. They usually are under control by quite different organisational units, sometimes not really knowing anything about SAS and SAS applications.
So that is why I am looking for ways to avoid that.

(I confess I can see that those other organisational units might consider streaming that kind of code from SAS a security risk...)
But it should be possible to download the Bootstrap and jQuery code, and stream it to _webout.

AllanBowe · Posted 10-16-2023 11:08 AM

actually, there is a way you can still keep your web app contained in your SAS code, and stream everything through WEBOUT, and comply with CSP

We manage it with Data Controller - one SAS program (demostream_sas9.sas) deploys the entire app: https://git.datacontroller.io/dc/dc/releases

An overview of the technique is described here: http://sasapps.io/sas-streamed-apps

/Allan
SAS Challenges - SASensei
MacroCore library for app developers
SAS networking events (BeLux, Germany, UK&I)
Data Workflows, Data Contracts, Data Lineage, Drag & drop excel EUCs to SAS 9 & Viya - Data Controller
DevOps and AppDev on SAS 9 / Viya / Base SAS - SASjs

Developers

Setting Content-Security-Policy directives for Stored Process

Re: Setting Content-Security-Policy directives for Stored Process

Re: Setting Content-Security-Policy directives for Stored Process

Re: Setting Content-Security-Policy directives for Stored Process

Using Output Refinement in A SAS Customer Intelligence 360 Direct Mark...

Failed login to stored process server

SAS web server Content Security Policy blocks access to outside source...

Migration of Stored Processes to SAS Viya Jobs

SAS CI 360 Direct Agent Deployment Recommendation (M8)

Follow Us

What is...

Developers

Our biggest data and AI event of the year.

SAS Training: Just a Click Away

Follow Us

What is...