8
I've got a similar problem, but with a much more limited base of knowledge.
I would like to have my users authenticated with something external to XOOPS. I have no experience as a sys admin or anything close to that, so I need to know if it is feasible to set up LDAP on a shared server and then have XOOPS use it for authentication. (I think most xoopsers who want LDAP authentication are putting XOOPS into environments like intranets and extranets where they have their own servers. I can only afford shared hosting for my web sites.
I don't want to constrain my future web presence to using XOOPS only, and I don't want to force my users to register additional user names and passwords if I find more applications that I want to present to them. In other words, not everything is best delivered as a XOOPS module, so I'd like to get as close to a single sign-on as possible.
If XOOPS is set up to use LDAP, does that mean that the XOOPS registration process inserts the right information into LDAP, so that another application could also authenticate against the same LDAP?
If that is the case, then can I start with a fresh XOOPS installation and a fresh LDAP installation? As new opportunities arise in the future for applications other than XOOPS, I can integrate them with the existing LDAP, assuming they have that capability. (That's still a broader opportunity than just waiting for cool new XOOPS mods. I think XOOPS mods are great, but that's expecting too much from them, I think.)
Where should a novice start with all of this?
Thanks,
Jim