|
| Field |
|
| Field description |
|
| Usage tips |
|
|
|
|
|
|
|
| |||
|
|
|
|
| If you select either Domain or LDAP |
|
| Understanding groups and users): |
|
|
|
|
|
| authentication, expand the LDAP server |
|
| Local: Only users with valid local |
|
|
|
|
|
| section and enter the details of a Microsoft |
|
| accounts added through the Groups & |
|
|
|
|
|
| Active Directory server. To enter details for |
|
| users page can log in. Local groups are |
|
|
|
|
|
| more than one LDAP server, click Add |
|
| not supported. |
|
|
|
|
|
| LDAP server. Currently, only Microsoft |
|
| Domain: Users with domain accounts |
|
|
|
|
|
| Active Directory Server is supported. |
|
| and local users are able to log in. The |
|
|
|
|
|
| Clicking Save checks the LDAP server |
|
| local administrator account can be used |
|
|
|
|
|
| settings because the Content Server |
|
| to configure the Content Server, or |
|
|
|
|
|
| attempts to bind to the LDAP server. |
|
| other local or domain users can be |
|
|
|
|
|
| Changes to this page are not saved if the |
|
| given a site manager role. Domain |
|
|
|
|
|
| LDAP server settings are incorrect. |
|
| authentication can only be used if the |
|
|
|
|
|
|
|
|
| Content Server has been added to a |
|
|
|
|
|
|
|
|
| domain. If you add the Content Server |
|
|
|
|
|
|
|
|
| to an existing domain, you need to |
|
|
|
|
|
|
|
|
| define a separate security policy for the |
|
|
|
|
|
|
|
|
| Content Server, otherwise the existing |
|
|
|
|
|
|
|
|
| security policies may prevent it from |
|
|
|
|
|
|
|
|
| functioning correctly. Contact your |
|
|
|
|
|
|
|
|
| authorized TANDBERG reseller or |
|
|
|
|
|
|
|
|
| partner for details of the recommended |
|
|
|
|
|
|
|
|
| security policy settings. The |
|
|
|
|
|
|
|
|
| recommended authentication mode for |
|
|
|
|
|
|
|
|
| a cluster is domain authentication. |
|
|
|
|
|
|
|
|
| LDAP: LDAP authentication does not |
|
|
|
|
|
|
|
|
| require the Content Server to be added |
|
|
|
|
|
|
|
|
| to a domain. Before changing |
|
|
|
|
|
|
|
|
| authentication from Local to LDAP, the |
|
|
|
|
|
|
|
|
| site manager must add at least one |
|
|
|
|
|
|
|
|
| LDAP user with the site manager role to |
|
|
|
|
|
|
|
|
| the Content Server. To do this, go to |
|
|
|
|
|
|
|
|
| Management Settings > Groups and |
|
|
|
|
|
|
|
|
| users and select Add groups or |
|
|
|
|
|
|
|
|
| users. Enter at least one valid |
|
|
|
|
|
|
|
|
| username in Site manager role. Under |
|
|
|
|
|
|
|
|
| LDAP authentication local users cannot |
|
|
|
|
|
|
|
|
| log in using the standard login method. |
|
|
|
|
|
|
|
|
| However, the local administrator can log |
|
|
|
|
|
|
|
|
| in by adding #page:login&rescue:true to |
|
|
|
|
|
|
|
|
| the end of the Content Server URL in |
|
|
|
|
|
|
|
|
| the browser. |
|
|
|
|
|
|
|
|
| ||
| Add LDAP |
| You can add up to five servers that the |
|
| Only active if you have selected Domain |
| ||
| server |
| Content Server will look up to authenticate |
|
| or LDAP as the Authentication mode. |
| ||
|
|
|
|
| users. |
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| Server |
| The IP address or DNS name of your |
|
| Only Microsoft Active Directory Server |
| |
|
| address |
| LDAP server. |
|
| is currently supported. |
| |
|
|
|
|
|
|
|
|
| |
|
| Port |
| Port 389 is the default port for most |
|
|
|
| |
|
|
|
|
| Domain Controllers. Global Catalog |
|
|
|
|
|
|
|
|
| Servers may use port 389 or 3268. |
|
|
|
|
|
|
|
|
|
|
|
| ||
|
| Base DN | The search base which the Content Server |
|
| The Content Server searches the object |
| ||
|
|
|
|
| uses to search for user records. (DN = |
|
| specified and any objects beneath it. |
|
|
|
|
|
| Distinguished Name) |
|
| The Base DN is a unique name for this |
|
|
|
|
|
|
|
|
| container. It typically consists of OU, |
|
|
|
|
|
|
|
|
| CN, and DC components. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TANDBERG Content Server printable online help | 93 |
| ||||||
