#176335 - 2007-05-18 03:04 AM
Re: Integrated windows authentication?
[Re: Richard H.]
|
NTDOC
Administrator
   
Registered: 2000-07-28
Posts: 11628
Loc: CA
|
Not very secure if IT has a key now is it 
I would not think a password change would matter, however I've seen it happen on two different machines/users so it could be a fluke, but if the data is that important you shouldn't mess with something a bit flaky (but up to whomever chooses to use it). I use PGP for stuff I want to be reasonably secure, though I'm not sure that's where he wants to go with this. I think he just wants a hook into the MS Authentication that's easy which would be nice but I don't know of any easy way without coding it.
|
|
Top
|
|
|
|
#176340 - 2007-05-18 09:49 AM
Re: Integrated windows authentication?
[Re: NTDOC]
|
Richard H.
Administrator
   
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
I found an old (Access 2000) KB article on security which was interesting reading: http://support.microsoft.com/default.aspx?scid=kb;en-us;165009
Also interesting is that user level security has been dropped in Access 2007, though it will continue to support Access 2003 MDBs withe user level security. I assume that this is because having all the security contexts on the computer make it too easy to crack.
The only real user security which is not filesystem related that I can see in Access 2007 is securing the (entire) MDB file with a single fixed password which is used to encrypt the data.
So I don't think that hooking into Windows Authentication is going to help - other than providing a login to the application, which is really just window dressing.
|
|
Top
|
|
|
|
#176375 - 2007-05-21 06:08 PM
Re: Integrated windows authentication?
[Re: NTDOC]
|
Shaba1
Fresh Scripter
Registered: 2005-08-20
Posts: 44
|
I need the same thing to a mysql database. I know I cannot ask my users to remember two passwords and they would complain if they had to enter a username and password more then once after they turned on the computer. I am just starting with kixtart so I have no solutions but I will watch this thread to see of someone comes up with one.
|
|
Top
|
|
|
|
#176377 - 2007-05-21 06:56 PM
Re: Integrated windows authentication?
[Re: NTDOC]
|
Shaba1
Fresh Scripter
Registered: 2005-08-20
Posts: 44
|
I need the same thing to a mysql database. I know I cannot ask my users to remember two passwords and they would complain if they had to enter a username and password more then once after they turned on the computer. I am just starting with kixtart so I have no solutions but I will watch this thread to see of someone comes up with one.
|
|
Top
|
|
|
|
#176388 - 2007-05-22 09:55 AM
Re: Integrated windows authentication?
[Re: Shaba1]
|
Richard H.
Administrator
   
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
I need the same thing to a mysql database.
Please start your own thread.
The answer to your question is in the MySQL security FAQ which you can find at http://dev.mysql.com/doc/refman/5.0/en/faqs-security.html#qandaitem-26-9-4
Specifically the entry:
26.9.4: Does MySQL 5.0 have built-in authentication against LDAP directories?
No. Support for external authentication methods is on the MySQL roadmap as a “rolling feature”, which means that we plan to implement it in the future, but we have not yet determined when this will be done.
In other words, no, there is no simple way to integrate AD authentication.
If you only need lightweight security, you could get around the problem by implementing a simple password system. Either use the username as a seed to generate a pseudo-random password, or use something like the users SID as the password. This would allow you to automatically connect to the DB without making the user enter a password.
If you use the SID make sure that you reverse it, so that the most significant part is at the start!
The hash method is better, as it means users cannot easily guess the password of another user. It also measn that you can later change all the passwords by tweaking the password generation mechanism if it is discovered - either by changing the password generation script or perhaps by keeping a "salt" value on a read-only share.
In either case, you will need to ensure that the script is tokenised, otherwise your users will be able to read / copy the code and break in.
|
|
Top
|
|
|
|
Moderator: Shawn, ShaneEP, Ruud van Velsen, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Mart
|
0 registered
and 874 anonymous users online.
|
|
|