FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafone.com]
> Sent: August 4, 2003 4:36 AM
>
> > [ENCPPP]
> >         host = encppp.encompass.enc
> >          port = 1433
> >          tds version = 7.0
> >      try domain login = yes
> >      try server login = no
...
> > Note to list:  Does anyone want to test this, and preferably 
> > fix it?  A server may be configured to accept both kinds of 
> > logins.  It would be nice to try both in turn before 
> > reporting a failure, because per-connection there's no way to 
> > specify the type.  
> 
...
> Another way is to leave all blank and use "domain\username" syntax for
> user.

I like that idea.  If the username has either of the the forms:

        domain\username
        \\domain\username

we know to use a domain login.  If there's an "nt domain" entry, we know to
use a domain login.  Else we use a normal server login.  That's unambiguous,
nonredundant, and declarative.  

Microsoft logins may contain a '/', so we can't easily support
"domain/username".  

> IMHO it's not difficult to change this stuff... We should decide a
> method, patch (documentation and code) for 0.62 release...

Agreed.  Is there any reason to continue to call it "experimental"?  

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.