Noob Question - Client Server Installs

[jthompson333]

I've only been doing web development for a couple of years now. I'm mainly a Linux Admin geek with quite a bit of Multivalue Database experience. So forgive the rather rookie question.

I was intrigued by your login system, because I have put many hours in trying to figure out how to build one without using bulky CMS systems.

So if I just have one web server that I'm using your single sign on system with, do I have to install the client and the server piece on that web server?

You also mentioned I would need more than one client install?
Would that be the case for a typical LAMP Server (assuming you were building your website on that server).

[thruska]

Actually, the SSO system is a fairly complex piece of software because of what it is designed to do (massively scale). So I'm not surprised that you have questions. No need to apologize.

Even if you install it on just one server, both the SSO server and SSO client are required. If you add another domain somewhere or start clustering, the SSO server can be moved to its own area and your application remains unaffected other than the client needing minor configuration changes. On a single host with a single domain, I realize it is a bit overkill, but it actually works out pretty well even in that situation. You can focus on developing the application and leave the login system details up to the SSO server.

I install the client twice in two different locations. The reason I do this is because I want logins to not last as long for admin tools, to force the user to login to admin tools even if they are logged in elsewhere (possibly using a separate login), and the field/tag mapping requirements for the SSO server are different from the application's requirements. As a result, the SSO server gets its own client install to protect the SSO server admin and the application that you write gets its own client installation.

Let me know how it goes and don't be afraid to ask questions.