How do I make it so that multiple people can log into the admin area of the latest LinksSQL 2 Beta using different login names and passwords.
Dec 9, 2000, 2:04 AM
Novice (19 posts)
Dec 9, 2000, 2:04 AM
Post #1 of 3
Views: 1794
Dec 11, 2000, 12:34 PM
Administrator (9387 posts)
Dec 11, 2000, 12:34 PM
Post #2 of 3
Views: 1718
Hi,
You would need to edit the .htaccess and .htpasswd file manually. We may look at making this an option from within the admin.
Cheers,
Alex
--
Gossamer Threads Inc.
You would need to edit the .htaccess and .htpasswd file manually. We may look at making this an option from within the admin.
Cheers,
Alex
--
Gossamer Threads Inc.
Dec 11, 2000, 12:41 PM
Veteran (17240 posts)
Dec 11, 2000, 12:41 PM
Post #3 of 3
Views: 1719
Alex,
Couldn't there be an extra table called User_Status that is an AKO table that stores:
ID
UserID
StatusID
Then you could have a table called Status, which includes the following values:
ID
Status Name (*)
(*) Like Administrator, Editors, Employers, Managers, Registered
Then you can AUTHENTICATE users not only based on one status, but multiple statuses. This would allow people to be both registered (to add links, modify links, etc.) from the public interface scripts (add.cgi, modify.cgi) and also access the admin.cgi.
I have this almost working in Links SQL v.1.12...I don't think it would be complicated to add the above as a plugin or re-write some of the authentication codes in Links SQL 2.0 that verifies the User based on their Status ID rather than the "Status" field in the Users table.
Just a suggestion.
Regards,
Eliot Lee
Couldn't there be an extra table called User_Status that is an AKO table that stores:
Code:
ID
UserID
StatusID
Then you could have a table called Status, which includes the following values:
Code:
ID
Status Name (*)
(*) Like Administrator, Editors, Employers, Managers, Registered
Then you can AUTHENTICATE users not only based on one status, but multiple statuses. This would allow people to be both registered (to add links, modify links, etc.) from the public interface scripts (add.cgi, modify.cgi) and also access the admin.cgi.
I have this almost working in Links SQL v.1.12...I don't think it would be complicated to add the above as a plugin or re-write some of the authentication codes in Links SQL 2.0 that verifies the User based on their Status ID rather than the "Status" field in the Users table.
Just a suggestion.
Regards,
Eliot Lee