MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2012

Re: Security for SQL functions



fixed

Not necessarily....

I could foresee the function being dropped from the SQL catalog but
the *SRVPGM not being able to be deleted...

You need to look at the authorities required for create/drop, to
create a functions for instance:
Authorization
The privileges held by the authorization ID of the statement must
include at least one of the following:
v The privilege to create in the schema. For more information, see
“Privileges necessary to create in a schema” on page 18.
v Administrative authority
The privileges held by the authorization id of the statement must
include at least one of the following:
v For the SYSFUNCS catalog view and SYSPARMS catalog table: – The
INSERT privilege on the table, and – The system authority *EXECUTE on
library QSYS2
v Administrative Authority
The privileges held by the authorization ID of the statement must
also include at least one of the following:
v The following system authorities: – *USE to the Create Service
Program (CRTSRVPGM) command or
v Administrative authority

Charles

On Thu, Sep 13, 2012 at 3:50 PM, Dean Eshleman
<Dean.Eshleman@xxxxxxxxxxxx> wrote:
Thanks for the response. The service program behind the SQL function is secured appropriately, so I guess I'm covered.

Dean

On 9/13/2012 3:16 PM, Bob P. Roche wrote:
It might be easier to control the authority to the object rather than
those commands, Hopefully the commands are already secured so only
developers can CRTBNDRPG for example. But if those developers should not
be able to touch your function, I'd look at the authority settings on the
function.




From:
"Monnier, Gary"<Gary.Monnier@xxxxxxxxx>
To:
Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>,
Date:
09/13/2012 02:11 PM
Subject:
RE: Security for SQL functions
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Dean,

A couple of ideas...

On the IBM i a function is an object. Objects can be secured. Secure
your system so only selected individuals can CREATE and/or DROP objects.
This may mean restricting who can use some of the CRTxxxxxxx (CRTBNDC,
CRTBNDCPP, CRTBNDRPG, etc) commands.

For external products using ODBC/JDBC you can use an exit program to
interrogate inbound SQL strings for the functions you want to restrict and
reject the transaction if the user isn't authorized to the function(s).

HTH.

Gary

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dean Eshleman
Sent: Thursday, September 13, 2012 11:56 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Security for SQL functions

I am getting ready to put my first SQL user defined function into
production. I just discovered that apparently anyone can create a
function and also, anyone can drop a function. How do I secure my
production functions so that only certain people can drop them?

Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com>






________________________________________
Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do not
use or disclose this information. If you received this e-mail in error,
please delete or otherwise destroy it and contact us at (800) 348-7468 so
we can take steps to avoid such transmission errors in the future. Thank
you.
_______________

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com>






________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.
_______________

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact