How to centralise authentication to one file?

[Skeeve Stevens]

Hey all..

Does anyone know of any easy way to centralise the Usernames and Passwords to one file in a database?

When you migrate its really painful and if you have 20 files, you have to log in 20 times... its causing untold pain at the moment.

...Skeeve

[transpower]

Have 20 tables in one file, not 20 files (you have v. 7). Then you just login once.

[Ender]

I think security management is not supposed to be the driving criteria for whether you use one file with many tables, or many files.

There is a way to manage security accross multiple files, but it takes some thought to set up (or Fenton or Vaughn may posted an example somewhere in this forum.)

You can do most of it with the account management script steps; you can add accounts, enable or disable accounts, and change passwords. So each file would have scripts to do the appropriate action, and it would be initiated from a master calling script.

Check past articles in this forum for more details.

[RalphL]

If all files have the same passwords, you should only have to login once.

[Steven H. Blackwell]

OK, security schema ought not be the driving force behind solution architecture. The data model and the business rules should cover that. if you have lots of files, use external authentication.

[smorr]

See my recent post in the Spotlights forum

In a Gui/Data separation model, you set the user passwords for the front end database, and set passwords based on privileges for the backend database(s). The frontend database will relogin to the backends as need be with appropriate privileges to the user. They way, passwords are easier to manage and user can change password at will.

Post on password management