In <[EMAIL PROTECTED]>, Mike Amburn
([EMAIL PROTECTED]) in a fit of unbridled passion, wrote:
> every application i've worked with in the past stored user information
> within database tables: get user name from the "user" table, and so on.
> however, as distributed architectures seem to becoming more and more
> integrated with application servers, i've wondered how something like LDAP
> plays into managing user information. it seems having a directory server
> manage user information across multiple applications in an open architecture
> is more appealing than using proprietary database tables.
>
> is anyone using a directory server (via LDAP) to store user information? if
> so, are you sharing the directory server with other applications or
> networks?
>
> is anyone using a directory server to authenticate users?
>
> what basic advantages does a directory server offer a CF-based application?
> disadvantages?
For enterprise applications, LDAP kicks butt. It contains all username
and password data, allows authentication, and can be bolted on to NT,
2000, Linux, .. just about everything. It's great for giving users a
single username and password in one place and forgetting about it.
There's no real value to using it if you're just writing an app that is
standalone in the sense that users logging into it won't be logging into
another network service -- a file server or email server, for instance.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
