Re: In-house authentication & authorization

Apache really doesn't care where the content comes from. If you are
using apache to serve as the front end and using it's authentication,
then the auth occurs before any content is served. Node has it's own
built in web server however, and that is what is usually used when you
are using it. Java is usually served by something like tomcat or
websphere. It is possible to use apache as a reverse proxy for those
other web servers, and put apache auth on top.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Justin
Taylor
Sent: Thursday, December 22, 2016 1:46 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] In-house authentication & authorization

I know Apache can handle authentication for static pages & CGI, but what
about other things like PHP, Node, Java, etc?



-----Original Message-----
From: Bradley Stone [mailto:bvstone@xxxxxxxxx]
Sent: Wednesday, December 21, 2016 11:05 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] In-house authentication & authorization

Its easy to add authentication that uses the IBM i user ids and
passwords
with the apache server. I personally don't like basic authentication
but
in your case it would remove redundancy of ids and passwords.

Brad
www.bvstools.com


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