468,549 Members | 2,006 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,549 developers. It's quick & easy.

Allow DB2 acces through db2connect only from delimited clients

Hello,
I would like to known if it is possible to limit acces to a UDB
database on Solaris system through db2connect to only specified
clients ?
My client is a db2connect on Windows platform.

Thank you
Nov 12 '05 #1
4 2567
You can limit access to DB2 UDB on a Solaris server through use of the
os level userid/password definitions (etc/passwd) or via internal DB2
object-level and priviledge security. That limitation would be done via
userid/group .... I don't believe you can limit that access to specific
client machines from DB2.

By the way, you should be using a DB2 client to communicate directly
with the DB2 server on Solaris. DB2 Connect is only required to connect
to DB2 on the mainframe or AS/400.

Larry Edelstein

Kona wrote:
Hello,
I would like to known if it is possible to limit acces to a UDB
database on Solaris system through db2connect to only specified
clients ?
My client is a db2connect on Windows platform.

Thank you


Nov 12 '05 #2
I'm not sure if I understood your question correctly.

First of all you don't need DB2 Connect to connect a Win Client to a
Solaris box. All you need is a Db2 Runtime Client for Windows and the
correct database and node directory entries to address your database
on Solaris. If you want to limit access to specific users, you only
have to create those users as local users on your solaris box and set
DB2 DBM CFG parameter AUTHENTICATION to SERVER (which btw is the
default).

HTH
Joachim

ko*******@yahoo.fr (Kona) wrote in message news:<a1**************************@posting.google. com>...
Hello,
I would like to known if it is possible to limit acces to a UDB
database on Solaris system through db2connect to only specified
clients ?
My client is a db2connect on Windows platform.

Thank you

Nov 12 '05 #3
Sorry, my question was certainly not so clear.
My clients (Windows) are using an application that communicate via
ODBC to the UDB DB on Sun Solaris (Unix plateform).
We are using ODBC over a DB2Connect.
A db2Connect gateway server is using between the client and the UDB
server. So normally all request to the UDB are coming from the
db2Connect gateway.

The AUTHENTICATION parameter is already set to SERVER and local users
accounts are created onto the nix server. Each Unix group account are
granted to the UDB database.

Now all the security acces is set by the client application.
Suppose that someone can use the ODBC connection from MSQUERY, and now
is able to access the UDB tables without restriction (that normaly set
by the application).

So I would like to force that all request are coming only from the
db2connect gateway.

I do not known if now is a little more clear.

Thank you

Jo*******@email.com (Joachim Klassen) wrote in message news:<b5**************************@posting.google. com>...
I'm not sure if I understood your question correctly.

First of all you don't need DB2 Connect to connect a Win Client to a
Solaris box. All you need is a Db2 Runtime Client for Windows and the
correct database and node directory entries to address your database
on Solaris. If you want to limit access to specific users, you only
have to create those users as local users on your solaris box and set
DB2 DBM CFG parameter AUTHENTICATION to SERVER (which btw is the
default).

HTH
Joachim

ko*******@yahoo.fr (Kona) wrote in message news:<a1**************************@posting.google. com>...
Hello,
I would like to known if it is possible to limit acces to a UDB
database on Solaris system through db2connect to only specified
clients ?
My client is a db2connect on Windows platform.

Thank you

Nov 12 '05 #4
Sorry, my question was certainly not so clear.
My clients (Windows) are using an application that communicate via
ODBC to the UDB DB on Sun Solaris (Unix plateform).
We are using ODBC over a DB2Connect.
A db2Connect gateway server is using between the client and the UDB
server. So normally all request to the UDB are coming from the
db2Connect gateway.

The AUTHENTICATION parameter is already set to SERVER and local users
accounts are created onto the nix server. Each Unix group account are
granted to the UDB database.

Now all the security acces is set by the client application.
Suppose that someone can use the ODBC connection from MSQUERY, and now
is able to access the UDB tables without restriction (that normaly set
by the application).

So I would like to force that all request are coming only from the
db2connect gateway.

I do not known if now is a little more clear.

Thank you

Jo*******@email.com (Joachim Klassen) wrote in message news:<b5**************************@posting.google. com>...
I'm not sure if I understood your question correctly.

First of all you don't need DB2 Connect to connect a Win Client to a
Solaris box. All you need is a Db2 Runtime Client for Windows and the
correct database and node directory entries to address your database
on Solaris. If you want to limit access to specific users, you only
have to create those users as local users on your solaris box and set
DB2 DBM CFG parameter AUTHENTICATION to SERVER (which btw is the
default).

HTH
Joachim

ko*******@yahoo.fr (Kona) wrote in message news:<a1**************************@posting.google. com>...
Hello,
I would like to known if it is possible to limit acces to a UDB
database on Solaris system through db2connect to only specified
clients ?
My client is a db2connect on Windows platform.

Thank you

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

11 posts views Thread by Google Mike | last post: by
2 posts views Thread by Evelyn Schwartz via SQLMonster.com | last post: by
reply views Thread by Andreas Schmied | last post: by
1 post views Thread by lfo | last post: by
3 posts views Thread by updates4004 | last post: by
2 posts views Thread by Valentin via DBMonster.com | last post: by
reply views Thread by anokun7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.