ODBC and network security

Posted in 2000

Topics: Connectivity: ODBC / JDBC / .NET

BThomas@bv229.k12.ks.us — Wed, 17 May 2000 12:11:32 -0500 — source: Informix-list mailing list archive (1991-1998)

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFC022.F34EFF88 Content-Type: text/plain; charset="iso-8859-1" Hello all, Pardon me if this has been a recently discussed subject... We have Client SDK 2.30 (Intersolv 3.11/CLI 2.8) on Windows NT going to 7.31.UC3 IDS on HP. All of which works...too good. We did have users coming in via HP's Openlink, version 3.2, which allowed us to specify what users could connect to the server and even put a read-only status on them. We had to switch to CLI (because of Openlink problems coming from MS Access and going to Informix) The question is: Is there any way to limit users or give users read-only access with CLI as we had done with Openlink? Thanks in advance, Bill Thomas System Specialist, IS Dept. Blue Valley School District BThomas@bv229.k12.ks.us 913-681-4666 (phone) 913-685-7726 (fax) ------_=_NextPart_001_01BFC022.F34EFF88 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2650.12"> <TITLE>ODBC and network security</TITLE> </HEAD> <BODY> Hello all, Pardon me if this has been a recently = discussed subject... We have Client SDK 2.30 (Intersolv = 3.11/CLI 2.8) on Windows NT going to 7.31.UC3 IDS on HP.  All of = which works...too good. We did have users coming in via HP's = Openlink, version 3.2, which allowed us to specify what users could = connect to the server and even put a read-only status on = them.  We had to switch to CLI (because of Openlink problems = coming from MS Access and going to Informix) The question is: Is there any way to limit users or = give users read-only access with CLI as we had done with = Openlink? Thanks in advance, Bill Thomas System Specialist, IS Dept. Blue Valley School District BThomas@bv229.k12.ks.us 913-681-4666 (phone) 913-685-7726 (fax) </BODY> </HTML> ------_=_NextPart_001_01BFC022.F34EFF88--

↪ replying to BThomas@bv229.k12.ks.us

Wolfgang Zager — Thu, 18 May 2000 08:42:40 +0200 — source: Informix-list mailing list archive (1991-1998)

BThomas@bv229.k12.ks.us wrote: > > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01BFC022.F34EFF88 > Content-Type: text/plain; > charset="iso-8859-1" > > Hello all, > > Pardon me if this has been a recently discussed subject... > > We have Client SDK 2.30 (Intersolv 3.11/CLI 2.8) on Windows NT going to > 7.31.UC3 IDS on HP. All of which works...too good. > We did have users coming in via HP's Openlink, version 3.2, which allowed us > to specify what users could connect to the server > and even put a read-only status on them. We had to switch to CLI (because > of Openlink problems coming from MS Access > and going to Informix) > The question is: > > Is there any way to limit users or give users read-only access with CLI as > we had done with Openlink? > > Thanks in advance, > > Bill Thomas > System Specialist, IS Dept. > Blue Valley School District > BThomas@bv229.k12.ks.us > 913-681-4666 (phone) > 913-685-7726 (fax) > > ------_=_NextPart_001_01BFC022.F34EFF88 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> > <HTML> > <HEAD> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3Diso-8859-1"> > <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = > 5.5.2650.12"> > <TITLE>ODBC and network security</TITLE> > </HEAD> > <BODY> > > Hello all, > > > Pardon me if this has been a recently = > discussed subject... > > > We have Client SDK 2.30 (Intersolv = > 3.11/CLI 2.8) on Windows NT going to 7.31.UC3 IDS on HP.  All of = > which works...too good. > > We did have users coming in via HP's = > Openlink, version 3.2, which allowed us to specify what users could = > connect to the server > > and even put a read-only status on = > them.  We had to switch to CLI (because of Openlink problems = > coming from MS Access > and going to Informix) > The question is: > > > Is there any way to limit users or = > give users read-only access with CLI as we had done with = > Openlink? > > > Thanks in advance, > > > Bill Thomas > System Specialist, IS Dept. > Blue Valley School District > FACE=3D"Arial">BThomas@bv229.k12.ks.us > 913-681-4666 (phone) > 913-685-7726 (fax) > > > > </BODY> > </HTML> > ------_=_NextPart_001_01BFC022.F34EFF88-- Intersolv ODBC uses the same security mechanisms as Informix in general do. So You can limit user access using the GRANT and REVOKE statements from SQL. BTW: Don't use HTML wolfgang

↪ replying to BThomas@bv229.k12.ks.us

schatzy@my-deja.com — Tue, 23 May 2000 16:43:24 GMT — source: Informix-list mailing list archive (1991-1998)

Bill, What were the problems with Openlink and MSAccess? Did you try relinking your database agent per their instructions at http://www.openlinksw.com/info/docs/rel3doc/unix/relink.htm Sometimes the Openlink server-side agent component may need to be relinked to your exact version of Informix ESQL/C Regards, Stephen In article <8fulum$23e$1@news.xmission.com>, BThomas@bv229.k12.ks.us wrote: > > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01BFC022.F34EFF88 > Content-Type: text/plain; > charset="iso-8859-1" > > Hello all, > > Pardon me if this has been a recently discussed subject... > > We have Client SDK 2.30 (Intersolv 3.11/CLI 2.8) on Windows NT going to > 7.31.UC3 IDS on HP. All of which works...too good. > We did have users coming in via HP's Openlink, version 3.2, which allowed us > to specify what users could connect to the server > and even put a read-only status on them. We had to switch to CLI (because > of Openlink problems coming from MS Access > and going to Informix) > The question is: > > Is there any way to limit users or give users read-only access with CLI as > we had done with Openlink? > > Thanks in advance, > > Bill Thomas > System Specialist, IS Dept. > Blue Valley School District > BThomas@bv229.k12.ks.us > 913-681-4666 (phone) > 913-685-7726 (fax) > > ------_=_NextPart_001_01BFC022.F34EFF88 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> > <HTML> > <HEAD> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3Diso-8859-1"> > <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = > 5.5.2650.12"> > <TITLE>ODBC and network security</TITLE> > </HEAD> > <BODY> > > Hello all, > > > Pardon me if this has been a recently = > discussed subject... > > > We have Client SDK 2.30 (Intersolv = > 3.11/CLI 2.8) on Windows NT going to 7.31.UC3 IDS on HP.  All of = > which works...too good. > > We did have users coming in via HP's = > Openlink, version 3.2, which allowed us to specify what users could = > connect to the server > > and even put a read-only status on = > them.  We had to switch to CLI (because of Openlink problems = > coming from MS Access > and going to Informix) > The question is: > > > Is there any way to limit users or = > give users read-only access with CLI as we had done with = > Openlink? > > > Thanks in advance, > > > Bill Thomas > System Specialist, IS Dept. > Blue Valley School District > FACE=3D"Arial">BThomas@bv229.k12.ks.us > 913-681-4666 (phone) > 913-685-7726 (fax) > > > > </BODY> > </HTML> > ------_=_NextPart_001_01BFC022.F34EFF88-- > Sent via Deja.com http://www.deja.com/ Before you buy.

Related threads

Glossary

IDS (Informix Dynamic Server)