|
|
|
| LDAP/Active Directory
Integration |
| New LDAP/AD import and
integration tools for single-login access. |
| |
|
|
|
Other advanced web-based
collaboration tools may provide batch LDAP import
tools to import from your LDAP into their
application. This has become expected from
top-end web-based collaboration tools.
Now, however, bf.collaboration not only provides
these LDAP (Active Directory, Novell, Netscape,
etc.) import tools, but bf.collaboration may be
the first to also offer true LDAP integration
that allows users to use their global login to
access all bf.collaboration tools even when a user
profile has not been imported from the
organization's LDAP. |
| |
|
|
|
|
|
|
| |
|
|
Import directly from the
Administrator Console -- No batch scripting
necessary!
Even "advanced" web-based
collaboration tools often require you to create
and run a batch script each time to import users
from your organization's LDAP/AD service.
With bf.collaboration, the LDAP import process is
significantly simplified by providing
administrators with a simple graphical user
interface (GUI) displaying all available options,
and is already pre-populated with your
organization's default LDAP service information. |
|
| Advantages
with LDAP/AD Service Integration |
|
 |
Single Login.
No need for users to maintain separate login
information for bf.collaboration (or
bf.collaboration components) |
|
System-wide,
up-to-date information. As your
global user list is periodically updated in
bf.collaboration, user profile information
remains current. |
|
Automatic
bf.collaboration profile creation.
When a user is added to your Active
Directory (or Novell eDirectory, Netscape
Directory Server, etc.), they can immediately
log on to bf.collaboration -- even if their
Directory profile has not yet been imported
into bf.collaboration. |
|
LDAP Import
Graphical User Interface (GUI).
Unlike with some other web-based
collaboration tools, LDAP imports are
handled directly from the Administrator
console GUI, and require no text-based batch
scripting that can increase the chance of
erroneous import execution. |
|
|
|
|
|
|
| |
|
|
|
