Re: In-house authentication & authorization -- WEB400

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: In-house authentication & authorization
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Thu, 22 Dec 2016 19:46:02 +0000
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

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

Follow-Ups:

Re: In-house authentication & authorization , Bradley Stone
Re: In-house authentication & authorization , Kevin Bucknum
Re: In-house authentication & authorization , Nathan Andelin

This mailing list archive is Copyright 1997-2026 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.