A good discussion comes when an unic authentication is needed to web systems: the user have a SAMBA login and password to windows; another to *NIX; and lots of logins and passwords to general applications. These all are not useful!
The first solution was create a unic login and password to all application, loging on a unic data base, and the app consulting it. Wow, do we have a lack of security? Yes, we have a lot of application made by a lot of human beings, read it as “not perfect”, maybe one of them wants to do something bad.
Second solution: a unic SAMBA login. That sound fantastic to my ears, but, how do we do that? The sambapasswd is not a easy file to understand and ldap is “kill a fly with a bazooka”. So, the answer:
This software, made by Victor M. Varela, connect to the SAMBA server through smbclient and show the content of the user folder and create some session variables that is useful to authentication to the systems!
One time connect to SAMBA, there’s no more password needed because you have the session variables to authentication, so, you just need to make a database with “who user can connect to what”.
That’s all folks! Good work to everybody.
P.s: Fast writing, report erros, please! lol.
[...] Some days ago I looked for a easy way to access internal web application with a unic authentication, SAMBA authentication, and I found a good software to do it. Go see it! [...]
Pingback by Domain (SAMBA) server « Tech, music, madness and what comes out.. — July 31, 2007 @ 1:59 pm |