1
0
mirror of https://github.com/samba-team/samba.git synced 2025-02-05 21:57:51 +03:00

Added notes that this chapter is in flux.

(This used to be commit 1e42b2c6816ffd5b3656734e3c0804e81a43f503)
This commit is contained in:
John Terpstra 2005-06-19 15:21:11 +00:00 committed by Gerald W. Carter
parent 9c183bae31
commit 6a953e9f9e

View File

@ -266,7 +266,32 @@ administrative nightmare.
<para>
SSO implementations may involve centralization of all user account information in one repository. Depending on
... add stuff here JHT!
environmental complexity and the age of the systems over which a SSO solution is implemented, it may not be
possible to change the solution architecture so as to accomodate a new identity management and user
authentication system. Many SSO solutions involving legacy systems consist of a new super-structure that
handles authentication on behalf of the user. The software that gets layered over the old system may simply
implement a proxy authentication system. This means that the addition of SSO increases over-all information
systems complexity. Ideally, the implementation of SSO should reduce complexity and reduce administative
overheads.
</para>
<para>
JJJ More Info HERE!
</para>
<para>
Briefly describe: 1. New auth system that uses external auth.
2. SSO system that stores info about all IT systems, and provides front-end
app. that hides the IT systems beneath a veneer of its own.
3. Meta-directories and distribution if ID info.
4. The significance of Samba in the context of SSO
5. Implications of domain security
a) with NT4 domain
b) with ADS
</para>
<para>
Other considerations: Should this stuff go elsewhere? Should it be dropped? Should this chapter be revamped?
</para>
</sect1>