Re: In-house authentication & authorization -- WEB400

Subject: Re: In-house authentication & authorization
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 22 Dec 2016 13:32:58 -0700
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?

You'd need an application and a framework for handling:

1. Authentication.
2. Authorization.
3. Access (i.e. only show menus and menu items which users are authorized
to).
4. Opening multiple apps & toggling between them.
5. Setting Favorites.
6. Defining user/group authorities to resources.
7. An API to check user authorities to resources.

This is the type of infrastructure needed to build products with ERP-type
scope.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: In-house authentication & authorization , Justin Taylor
Re: In-house authentication & authorization , Mark Murphy/STAR BASE Consulting Inc.

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.