> > The only common denominator that could possibly cover all contingencies would
> > be LDAP authentication. One way of doing this in a more-or-less universal
> > fashion is to offload the auth task from eLog itself and place the burden on
> > Apache. This means figuring out how to get Apache to pass auth info to eLog
> > when eLog operates behind Apache. In the end, anything that can use LDAP as an
> > authentication mechanism (like AD) can host eLog - as long as eLog can glom off
> > of Apache's ability to do the actual authenticating.
>
> That sounds to me like a great idea. If anybody gets this working, people would be
> grateful if this could be submitted to the "Contributions" section of this forum.
Ah, you test me! Perhaps I will attempt to dig into this but I may have to leave the
integration up to you, Stefan. Seems that there would be two roads to go:
1> Move away from standalone and start to rely on Apache
2> Continue with the standalone theme and build in LDAP authentication (which could
also give you groups functions as well).
I think I would opt for <2> |