I'm starting my SingleSignOn journey. I don't want a way to authenticate to multiple machines, I want a way for virtual hosting customers to have an account name and password for accessing ftp, mail admin, webstats, and customer controlpanel (PHP app). Currently, these credentials are managed individually by the various services. To change a customer's password is a real pain, and I can't allow them to change their own password. Having the password stored in a mysql table would solve this.
libnss-mysql sounds perfect. It allows me to maintain a customer table where a username and password are stored. I can use these credentials to authenticate in my PHP apps as well as for the mail admin. In addition, I can configure ftp and Apache folders to authenticate against this table via libnss-mysql. Right?
That's correct -- no application (aside from your PHP customer self-management app) needs to be aware of MySQL - they'll behave just as if the user were in /etc/passwd.
As for libnss-mysql having more recent news -- libnss-mysql is in maint mode (bug/security fixes only, no new features). fssos hasn't had any recent updates because it's next update is really a huge rewrite and I haven't figured it out yet. If any bugs are found in either project, however, I'll fix them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for giving such a worthy project to the community, Ben.
I'm still not clear--I have a vague understanding that the 2 products overlap in the functionality they provide. So does FSSOS provide the same functionality that libnss-mysql does? Or do the products work together? Which should I install to accomplish my stated goal? Or both?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm starting my SingleSignOn journey. I don't want a way to authenticate to multiple machines, I want a way for virtual hosting customers to have an account name and password for accessing ftp, mail admin, webstats, and customer controlpanel (PHP app). Currently, these credentials are managed individually by the various services. To change a customer's password is a real pain, and I can't allow them to change their own password. Having the password stored in a mysql table would solve this.
libnss-mysql sounds perfect. It allows me to maintain a customer table where a username and password are stored. I can use these credentials to authenticate in my PHP apps as well as for the mail admin. In addition, I can configure ftp and Apache folders to authenticate against this table via libnss-mysql. Right?
Then I'm confused by a post by cinergi that seems to say FSSOS is the replacement for libnss-mysql. However, the news is more current at http://libnss-mysql.sourceforge.net/configuration.shtml than it is at http://fssos.sourceforge.net/index.shtml.
Can somebody help clear this up for me? Thanks a million!
That's correct -- no application (aside from your PHP customer self-management app) needs to be aware of MySQL - they'll behave just as if the user were in /etc/passwd.
As for libnss-mysql having more recent news -- libnss-mysql is in maint mode (bug/security fixes only, no new features). fssos hasn't had any recent updates because it's next update is really a huge rewrite and I haven't figured it out yet. If any bugs are found in either project, however, I'll fix them.
Thanks for giving such a worthy project to the community, Ben.
I'm still not clear--I have a vague understanding that the 2 products overlap in the functionality they provide. So does FSSOS provide the same functionality that libnss-mysql does? Or do the products work together? Which should I install to accomplish my stated goal? Or both?
Thanks.