On Fri, Mar 25, 2011 at 4:26 AM, Mircea Carasel <[email protected]> wrote:
> > > On Fri, Mar 25, 2011 at 9:51 AM, Kumaran < > [email protected]> wrote: > >> Hi All, >> If LDAP server is not running we cannot Authenticate the openfire >> and LDAP only for user Portal for LDAP user >> >> As a improvement >> If openfire and LDAP only authentication is enabled in setting Page >> and if LDAP server was not running then that time user in SipXecs should >> able to access the Xmpp account and user Portal.(ie when LDAP server was >> not running openfire and LDAP only authentication should need not be >> verified) So this improvement make sense? >> > Well, IMHO, I think that we should not blindly fall-back to database > authentication when ldap server is down. I think this > is confusing for the user > The superadmin can always log-in (superadmin always gets authenticated > against database) and verify the LDAP and if necessary > change the authentication scheme in the authentication settings page. > So what happens in the meantime if LDAP is down somehow? A user cannot login? Does this mean once LDAP is configured it is relying solely on LDAP and that user credentials are not stored and authed against directly from the local database. Since that is there shouldn't it be more "reliable" to have an auth service available than "not available" and requiring admin attention? If not, is there an alarm of any sort set against it to alert the admin before the angry mobs start banging on a door? > > Mircea > >> >> Thanks, >> Kumaran T >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
