[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::netrider

Title:	NetRider --- Remote Network Access Conference
Notice:	Please use keywords! See Note 2 for Directory of Important Notes
Moderator:	LAVC::CAHILLON

Created:	Tue Jan 24 1995
Last Modified:	Mon Jun 02 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	554
Total number of notes:	2264

549.0. "DRAS databases" by SANITY::LEMONS (And we thank you for your support.) Fri May 16 1997 09:44

    Hi
    
    In wandering your internal Web site, I'm sure I saw something that
    talked about DRAS' ability to, instead of using its own static
    database, use the authentication database of the node it ran on.  Is this
    true?  Where could I read the details about this?  Having just read the
    Use for Windows document, I didn't see this mentioned at all.
    
    My problem is a site where all three (OpenVMS, Digital UNIX, Windows
    NT) operating systems are used, and we have many instances of each. 
    The Windows NT world uses the DIGITAL1 domain, so has a common
    authentication database, but we have dozens of OpenVMS and Digital UNIX
    clusters/clumps.  I'd rather not have a static DRAS database if I could
    help it.  But I'm not seeing a way to use so many disparate
    authentication databases.
    
    If I have to have a static database, I'd rather it exist as a table in
    a SQL-compliant database.  This would give me the greatest hope of
    easily weaving it into existing databases.
    
    Thoughts?
    
    Thanks!
    tl

T.R Title User Personal
Name Date Lines

549.1 The HOST with the most... CSC32::R_BUCK Authenticated and assimilated Wed May 21 1997 20:22 18

T.R	Title	User	Personal Name	Date	Lines
549.1	The HOST with the most...	CSC32::R_BUCK	Authenticated and assimilated	`Wed May 21 1997 20:22`	18
	Going to guess that HOST authentication was the context where DRAS uses the native authentication database of the system where it is running. We have configured it for HOST authentication on Windows NT and OpenVMS. One of the current limitations is that you still have to add a record to the DRAS Server database for each user. Name must match the name in the native authentication database, (SYSUAF.DAT for example). Some great improvements are coming in this area though! What's not available today, and maybe not for a while, is the ability to have multiple DRAS servers on different platforms, replicate and/or communicate with each other to present one single authentication domain. Today, with a combination of realm names and multiple DRAS servers, you should be able to setup an environment where a user can be authenticated using a Username and Password combination that is the same as their Windows NT, OpenVMS, or Digital UNIX login. Randall Buck MCS - Network Support

    Going to guess that HOST authentication was the context where DRAS uses
    the native authentication database of the system where it is running. 
    We have configured it for HOST authentication on Windows NT and
    OpenVMS.  One of the current limitations is that you still have to add
    a record to the DRAS Server database for each user.  Name must match
    the name in the native authentication database, (SYSUAF.DAT for
    example).  Some great improvements are coming in this area though!
    
    What's not available today, and maybe not for a while, is the ability
    to have multiple DRAS servers on different platforms, replicate and/or
    communicate with each other to present one single authentication
    domain.  Today, with a combination of realm names and multiple DRAS servers,
    you should be able to setup an environment where a user can be
    authenticated using a Username and Password combination that is the
    same as their Windows NT, OpenVMS, or Digital UNIX login.
    
    Randall Buck
    MCS - Network Support