Re: Limit access to database tables in finance library using user exit QIBM_QDB_OPEN

[Brian Johnson <brian.johnson.mn@xxxxxxxxx>]

Take a look at database server exit points QIBM_QZDA*.

On Wed, Oct 19, 2022 at 6:18 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> An alternative is "Application Only Access".  Which basically says that
> the user has NO access to the data.  All access to the data is done instead
> by programs.  The way this is usually done is by having your application
> either adopt authority or use profile handles to then get access to the
> data.  This then allows you to not have to play "Whack-a-mole" trying to
> figure out all the various ways people may access the data.
> https://www.linkedin.com/pulse/piecemeal-security-rob-berendt/
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Sune Elvig via MIDRANGE-L
> Sent: Wednesday, October 19, 2022 5:08 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Cc: Sune Elvig <sune.elvig@xxxxxxx>
> Subject: Limit access to database tables in finance library using user
> exit QIBM_QDB_OPEN
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi
>
> I have been exploring different ways to limit the access to specific
> database tables when the query is done via ODBC or other remote access.
>
> I have been thinking about using the user exit QIBM_QDB_OPEN, but how do I
> know how the user is doing the query?
>
> --
> Med venlig hilsen,
> Best regards,
>
> *Sune Elvig*
> Application Manager DBS
>
> IT Competence Center PEPP
> Mileparken 22A, 2. sal | 2740 Skovlunde | Denmark
> *M *+45 20 75 99 31
> *E *sune.elvig@xxxxxxx | *I **http://www.pon-cat.com*
> <http://www.pon-cat.com/>
> ………………………………………………………………………………………
>
>
> _______________________________________________________________________
>
> Please consider the environment before printing this e-mail
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com