Re: In-house authentication & authorization

How would it supplement OS security?

I'm just suggesting that developers may supplement OS security by including
program logic which checks user authority to anything exposed by the
program (i.e. does a user have authority to approve a purchase order or
invoice?)

I'm suggesting that such logic can be part of a framework, so that it is
easy to implement.

If your server program is running as a named user, that will be the user

the OS uses for authorization regardless of the end-user (unless it does
user swapping like CGI).

We use a web portal which launches new IBM i JOBs when users click on menu
items. Those JOBs run under the IBM i user profile assigned to the users.
Each JOB handles requests pertaining to just that user. We don't "swap"
profiles like your CGI example.