|
From: <pe...@go...> - 2011-01-10 21:04:37
|
to add a thought to Jeroen's good reply... On 09/01/2011 07:27, Ben Carbery wrote: > Can any of the devs confirm whether or not this is worth trying to > do? If netdisco fundamentally relies on session information being in > the database and this can't be easily changed, then I am thinking > not.. My guess would be that if you enabled "Apache Auth" in Netdisco config (and Apache-Netdisco config) then the users and session tables would not be touched. If you have a more public frontend then this could use Apache Auth (as I used to do, with our org's single-sign-on and a "require user ..." or "require group ..." statement in Apache conf). It shouldn't stop any other instance using a different auth mechanism. Probably a good idea to disable the admin panel features altogether in this case as well. regards, oliver. |