Security Access. Any Help?

[Luis Moises Rojas]

My App need to CONNECT to a Server(SQL). I need to KNOW the user and password in order to connect to the DATABASE. The Question is:

1. If i know the USER AND PASSWORD Where is the "SECURITY"?
2. How can i connect to a database calling the user and the password without Knowing ? I meant, if there is a way to have the user and password on a file(script of course) or anyother way?

[Pasvorto]

in DAO:
dim db as database

Set db = DBEngine.Workspaces(0).OpenDatabase("C:\DATABASES\Database.MDB", False, False, ";pwd =fred;")

in ADO

dim CnXn as ADODB.Connection
Set Cnxn = New ADODB.Connection
strCnxn = "Provider=Microsoft.Jet.OLEDB.4.0;Jet OLEDBatabase Password =condon;Data Source=C:\DATABASES\Database.mdb;Jet OLEDB:Engine Type=4;"
Cnxn.Open strCnxnTech

[Pasvorto]

Last line should read:

Cnxn.Open strCnxn

[Luis Moises Rojas]

Yes, my friend i agree with you. but i still know the password and the user. What i need i to GET the password and the user from somewhere as a variable and pass those values to SQL or ANY DATABASE, but without KNOWING THE VALUES.

Is that possible?
Should I have to have those values always on my program or on a INI FILES?

[vb_dba]

I would recommend storing those values in the registry. Then just read the registry at startup and store the values in a global variable.

Here are some links to show you how:
Using GetSetting/SaveSetting
Using API

[Pasvorto]

I find the problem with storing that data in the registry is that by using regedit, you can see the "secure" data.

By having it in my source code, I control who can see it (nobody but me).

[vb_dba]

If you encrypt the data in the registry, it shouldn't be a problem. I would rather use the registry to store this data than an INI file as end-users are most likely more comfortable with using Windows Explorer (if the O/S is Windows based) than using regedit.

If you always want to log on using the same ID, and you know there is no chance that that ID will be dropped, then you could probably go ahead and hard code the ID and password in your app.

[Wydok]

How is your program running? If it is interactive, prompt the user for his/her name and password. If it is scheduled, schedule using a windows NT/2000 account, and give that account access to SQL Server.

Or you could store in the registery, but definetly encrypt the password.

[rdrouill]

If you are looking at Encrypting I found this thread posted in General VB Questions which may be of help for you



http://www.vbforums.com/showthread.p...hreadid=211187

[Beacon]

Yo no need for all that jazz.

It's an SQL server db...

cn.Provider = "sqloledb"
cn.Properties("Prompt") = adPromptAlways
cn.Open "Data Source=TheServerName;" & _
           "Initial Catalog=TheDatabaseName"

This will prompt for username and password.

That way you dont code it, it's up to the user.
Else you ask them to enter it in a login form.

good luck
b