Re: Apache authentication efficiency

Would you be against rolling your own using cookies/tokens? It's how I've
done it on quite a few projects. And it's how a lot of larger sites do
things.

On Thu, Jan 30, 2020 at 4:49 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

" You can license our web portal."
We don't really buy software. It would have to be included in IBMi or
FOSS.

" I'm not aware of any other options on any platform, IBM i or otherwise."
Hmm... I can't believe I'm the only one concerned about this. Of course,
there is your commercial solution and may be others.


Thanks



-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Thursday, January 30, 2020 4:46 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx

Subject: Re: [WEB400] Apache authentication efficiency

On Thu, Jan 30, 2020 at 11:10 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

I'm hoping for more specifics. Ideally, I'd like a lead I can
research, prototype and implement.

You can license our web portal. Another alternative that I can think of
may be based on OA. Vendors generally implement a JavaScript application
that is functionally comparable to a 5250 emulator. That client
communicates with an OA server that is generally implemented within a
persistent CGI process. I suspect those servers only authenticate once (at
the server's entry point), then rely on the persistent connection after
that.

I'm not aware of any other options on any platform, IBM i or otherwise. I
think the common practice is to check the credentials of the user and check
user authority for every resource requested, because the interfaces are
stateless. Developers either rely on an HTTP server for that. Or they add a
call within every application to a routine that authenticates the user and
checks their authority.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.