|
>From the intro articles/diagrams I looked at, it [EIM] seemed mostly like >a way for two systems to map (already authenticated) >usernames between each other. That's my understanding too. Are you saying that PAM provides a way to describe the objects that are the be secured? Single-signon is great, but the bigger problem is figuring out how to restrict access within an application. How do I specify what users can access a given vendor, or what users can read the salary row? And how do I do this when the "user" is question isn't an operating system user, but a record in the users table? Oh, and this all should include the ability to adopt authority from multiple parent records. If PAM provides a nice way to solve these problems please point me there. -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
