Masking Stored Process Code for EG Users?

[kruzewski]

Is it possible to either mask the sas code of a stored process for an EG user OR prevent them from looking at its metadata while still allowing them to run it...?

[Quentin]

Hi,

I suppose one way to hide the "source code" of a stored process would be to have the actual stored process be just a macro call.  Then macro definition could be stored in another file, or even a compiled macro catalog, or similar.

--Q.

[kruzewski]

wouldn't the user still need access to the "source code" of the macro?....btw, I wanted to create a SP which would allow an end user to kill their own sessions if something hangs, BUT I don't want them to know how to run an x command on the windows server...

[Quentin · Accepted solution]

Hi,

On the server, you can compile the macro and store the definition in a permanent macro catalog.  In v9.2, you can even encrypt the compiled catalog, but that may be overkill for your needs.

See http://support.sas.com/techsup/technote/ts739.pdf, search for SECURE.

So the only thing on the server the user needs read access to is the encrypted macro catalog holding the definition of %KillSession().

Pretty sure that should work for you.

Not sure what you will put as the definition of %KillSession(), or how the stored process server or workspace server will feel to have somebody else killing jobs...

--Q.

[kruzewski]

I just key it off of &sysuser. so they they are only able to kill their own

[kruzewski]

...and thanks!