On Sun, Jun 27, 2010 at 6:24 PM, Todd Hodgen <[email protected]> wrote: > Can you clarify - There will now be a configuration that one would select > that requires LDAP for login, and if not selected, then they continue to use > the existing login?
Yes, there will be an option to enable that. So to consider this with the parallel ldap work going on for openfire, and as I understand the design so far, you will be able to do any of the following: Scenario 1 - "as it is today" Use LDAP to build users for sipxconfig Use LDAP to build users for openfire Manage web portal credentials in sipXconfig Scenario 2 - "Not that into LDAP for Openfire" Use LDAP to build users for sipxconfig Use LDAP to build users for openfire Use LDAP to authenticate non-admin users in web portal Scenario 3 - "Not that into LDAP for Web Portal" Use LDAP to build users for sipxconfig Use LDAP manage and authenticate users in openfire ** Manage web portal credentials in sipXconfig Scenario 4 - "LDAP Deluxe" Use LDAP to build users for sipxconfig Use LDAP manage and authenticate users in openfire ** Use LDAP to authenticate non-admin users in web portal ** The trick here is to use the LDAP field mapping table configured in sipXconfig for sipXconfig users AND openfire users. One user interface, configuring two system's ldap interfaces. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
