Re: Trusted connections
From: Alin Sinpalean (alin_at_earthling.net)
Date: 04/23/04
- Next message: Alin Sinpalean: "Re: JDBC and SQL server Stored procedure exception"
- Previous message: Joe Weinstein: "Re: JDBC and SQL server Stored procedure exception"
- In reply to: Sue Purkis: "Re: Trusted connections"
- Next in thread: Sue Purkis: "Re: Trusted connections"
- Reply: Sue Purkis: "Re: Trusted connections"
- Messages sorted by: [ date ] [ thread ]
Date: 23 Apr 2004 05:28:40 -0700
>From the JNetDirect site (JSQLConnect Technical Reference):
[quote]
The components required to use trusted authentication with JSQLConnect
are:
The file JSQLTrustedAuthentication.dll from your distribution must be
deployed in the system path (not necessarily the Java classpath) of
the machine from which the JDBC connection is made. The DLL is loaded
using Java Native Interface (JNI). For example, the DLL could be
deployed to \WINNT\system32.
Microsoft Data Access Components (MDAC) must be installed on the
machine where JSQLConnect is installed. The latest MDAC can be
downloaded from http://www.microsoft.com/data/
[/quote]
So how about the "no dll's on the client"?
Alin.
suepurkis@yahoo.com (Sue Purkis) wrote in message news:<e29f757e.0404211818.6fb7e01a@posting.google.com>...
> DatDirect offers a driver which supports Trusted Connections.
>
> jNetDirect's driver supports connection to SQL Server using Trusted
> Connections through the NTLM network authentication protocol.
> DataDirect's type 4 JDBC driver supports connecting to SQL Server
> using Trusted Connections through Kerberos. Kerberos is the default
> network authentication protocol available with Windows domain
> controllers running Active Directory. Using Kerberos, which Microsoft
> says is the most secure method of authentication, requires no dll's on
> the client -- maintaining the type 4 architecture.
>
>
>
>
> bruce_robertson01@yahoo.com (Bruce Robertson) wrote in message news:<c7c56b2c.0404120516.5ff5eff3@posting.google.com>...
> > Joe Weinstein <joeNOSPAM@bea.com> wrote in message news:<40746A88.9000906@bea.com>...
> > > Bruce Robertson wrote:
> > >
> > > > alin@earthling.net (Alin Sinpalean) wrote in message news:<a14fec3f.0404052355.162571d8@posting.google.com>...
> > > >
> > > >>Joe Weinstein <joeNOSPAM@bea.com> wrote in message news:<OWQMEvyGEHA.712@tk2msftngp13.phx.gbl>...
> > > >>
> > > >>
> > > >>>See the driver from http://www.jnetdirect.com. They offer this feature.
> > > >>
> > > >>Or jTDS (http://jtds.sourceforge.net) for a free alternative. However,
> > > >>with jTDS you will have to provide the Windows username and password,
> > > >>even if you are logged in because jTDS is a type 4 driver and as such
> > > >>cannot obtain native information such as Windows credentials.
> > > >>
> > > >>Alin.
> > > >
> > > >
> > > > Ok so please explain how you are claiming that the connection is
> > > > trusted if we still need to provide a username and password on the
> > > > connection?? Maybe I dont understand.. but I thought the whole
> > > > advantage of having a trusted connection is that we dont need to
> > > > supply user and password.
> > > >
> > > > -Bruce
> > >
> > > Alin is trying to underscore a feature of the jTDS driver, that you do
> > > not need to configure the DBMS users with DBMS passwords if you use
> > > the jTDS driver, if you give the driver the Windows user name and password.
> > > I also understand your position. Most people don't want to code their
> > > Windows username and password into a Java program, or require people
> > > to type them in at runtime. Those concerns are the brunt of what
> > > most people want from 'trusted connections'.
> > > As such, no pure type-4 JDBC driver can offer that, as I said before.
> > > The jnetdirect driver I quoted offers a small DLL with it's driver, which
> > > if installed on the client machine, will allow their otherwise-all-java
> > > driver to do what you want, connecting the Java application to the DBMS
> > > as the current Windows user, without coding or entering any username or
> > > password at runtime.
> > > I have no relationship with jnetdirect. I support JDBC for BEA, and I
> > > help with just about every driver in commercial use.
> > >
> > > Joe Weinstein at BEA
> >
> > Ok - thanks Joe. So as you have pointed out trusted authentication
> > provides two areas of advantage. 1) removes the requirement to
> > establish database accounts for every user 2) removes the requirement
> > to supply user/password on a database connection. So the jTDS driver
> > acheives 1) but not 2).
> > -Bruce
- Next message: Alin Sinpalean: "Re: JDBC and SQL server Stored procedure exception"
- Previous message: Joe Weinstein: "Re: JDBC and SQL server Stored procedure exception"
- In reply to: Sue Purkis: "Re: Trusted connections"
- Next in thread: Sue Purkis: "Re: Trusted connections"
- Reply: Sue Purkis: "Re: Trusted connections"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
