Understanding groups & users
Cisco TelePresence Content Server 4.1 printable online
Page 77 of 121
Note: Before changing au thentication mode t o LDAP, a site manager must add at least one LDAP
group or user with th e site manager role to the C on tent Server. Under L DAP authentication, local
users (that is user acco unts set up through the web interface for Wi nd ows Server administration on
the Content Server mach ine) including th e local administrator ca nnot log in using the log i n dialog.
However, the local administrator can log in by adding #page:login&rescue:true to the end of the
Content Server URL in the browser:
http://<ContentServerIPaddress>/tcs/#page:login&rescue:true.
Active Directory and yo ur Content Server is in th e same domain as your groups and user s
1. Go to Management settings > Site settings. S ee Configuring site settings.
2. For Authentication mode select Domain.
3. So that the Content Ser ver ca n obtain group inform ation, enter the det ails of your LDAP server
or servers.
4. Go to Management settings > Groups and users. See Adding and updating groups & users.
5. Add the domain groups or u sers to the Content Server i n the format group.n ame or
DOMAINNAME (optional)\user.name: Di sp lay Name(optional)>, an d assign the correct Rol e
(Viewer, Creator or Site manager).
o If Allow Guest Acc es s is enabled in Site settings, you n eed to manually add all t he groups
and users who you want t o l og in. If a user does not exist on the Content Serve r b efore
they attempt to log i n for the first time, but a group to which they belong does, their account
will be created autom atically and they will b e given the role of viewer . When the user logs
in, their role will be whichever is higher of t heir group role or thei r individual user role.
o If Allow Guest Acc es s is turned off in Site settings, you only need to add the groups and
users who need a role hig her than viewer (that i s, creators or site manag ers). If a user
does not exist on th e Content Server before th ey attempt to log in for t he first time
(regardless of wheth er there is a group add ed to the Content Server th at they are a
member of), their accou nt will be created aut omatically and they will b e given the role of
viewer. When the user logs in, their role will be whichever is higher of their group role or
their individual user role.
6. All users and all member s of the added groups now autom atically have access t o the Content
Server using their n ormal Active Directory use rname and password. Groups and users who
have been added to th e C on tent Server are listed i n the Displaying the G roups & users list: go
to Management settings > Groups and users. Their role is displayed n ext to the name. Note
that users m ay have inherited a hig her role from their gr oup membership than the on e d isplayed
but they can find out their role after they have logged in by going to their Preferences. See
Editing user prefe r ences.
You do not use Active Directory
1. Create local user accoun ts on the Content Server for every user individ u ally: go to
Management settings >Windows server and create the accounts in the n ormal way.
2. Go to Management settings > Site settings. S ee Configuring site settings.
3. For Authentication mode select Local.
4. Go to Management settings > Groups and users. See Adding and updating groups & users.
5. Add every user individu ally to the Content S er ver in the Add groups or users page with the
correct role (viewer, creator or site manag er). See Adding and updating groups & u sers. Local
users must be entered in the format: MACHINE NAME\user.name:Disp lay Name (optional). Not e
that local authen tication does not supp ort groups.
6. All users now have access to t he Content Server usi n g the username and passw ord of their
local account. Th eir role is the one assign ed to them individually.
Users who have been add ed to the Content Server are listed in the Display i ng the Gr o ups &