×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
QUSER should have NO authority to that user profile. That job does a "profile swap" to the user named in the ODBC connection. In all the new SQL services I think one is called job_user and the other is current_user, or maybe not, but basically they are different.
So if I do an ODBC connection you may see the job 138882/QUSER/QZDASOINIT, but the current user profile will be ROB.
So how does the program used by QUSER get authority to ROB to be able to do a profile swap to ROB? That's a secret known but to IBM. Mere mortals like us would use adopted authority, and then that adopted program would then use the profile swap APIs to do the profile swap. IBM has other techniques. If you really get into security audit monitoring all the time I see jobs temporarily getting ahold of QSECOFR but none of them are using adopted authority. It's mind numbing. I have a project to hunt these down but there are so many by IBM it's drowning.
Again, profile swapping is not the same as adopted authority. Mortals use adopted authority only so they can do profile swapping.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
