Adobe 65029902 User Guide - Page 18

Authenticate LDAP users, Important

Page 18 highlights

USING ROBOHELP SERVER 8 15 Managing the server Important: You cannot make this area protected and it cannot be deleted. To make an area protected, you can select the Protected area option in the Users page of the Web Admin interface. You can define several sets of privilege groups and assign different rights to different users. These rights include view only, publish, admin rights, and viewing reports. You can manage the groups and their privileges from RoboHelp Server Web Admin pages. RoboHelp Server 8 provides user authentication through both database and LDAP. Authenticate LDAP users You can use the _server.properties file to authenticate an LDAP user or an administrator. Do the following: • Comment the authtype = db property, specify your LDAP username in the DefaultAdminUid property, and do not specify your LDAP password in the DefAdminPwd property. • Uncomment and specify your organization LDAP details: authtype = ldap ldapURL = ldap://ldapserver:389 usersearchbase = ou=people,o=org rolesearchbase = ou=groups,o=org useridkey = uid rolename = cn rolesearch = uniqueMember • Restart the Tomcat service to log in as an LDAP user. The following table lists the properties stored in the _server.properties file: Property Name DatabaseType DSN authtype ldapURL usersearchbase rolesearchbase useridkey rolename rolesearch DefAdminUID Description Property Value Required (Yes/No) Specifies the database used oracle/access/sql (access by default) Yes (supported types are oracle/access/sql) If oracle or sql database, specifies the DSN name dsn used to connect to database required for Oracle and SQL databases Specifies the authentication db/ldap yes mechanism used. LDAP server URL URL of LDAP Server of the organization if authtype is ldap User search base URL of LDAP Server of the organization if authtype is ldap Role search base Subcontext in LDAP server in which role information is stored if authtype is ldap User ID key which stores the User ID in user ID key the LDAP server if authtype is ldap Role Name key which stores the role role name key name in the LDAP Server if authtype is ldap Attribute to be searched in the role name role attribute name if authtype is ldap When server is started for the first time, User ID which has admin access to yes server is not connected to the RoboHelp Server by default. database. Therefore, access permissions for a given user cannot be verified. Provide a default user ID which has the admin rights and can access the web admin.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

15
USING ROBOHELP SERVER 8
Managing the server
Important:
You cannot make this area protected and it cannot be deleted.
To make an area protected, you can select the Protected area option in the Users page of the Web Admin interface.
You can define several sets of privilege groups and assign different rights to different users. These rights include view
only, publish, admin rights, and viewing reports. You can manage the groups and their privileges from RoboHelp
Server Web Admin pages. RoboHelp Server 8 provides user authentication through both database and LDAP.
Authenticate LDAP users
You can use the
<context-name>_server.properties
file to authenticate an LDAP user or an administrator. Do
the following:
Comment the
authtype = db
property, specify your LDAP username in the
DefaultAdminUid
property, and do
not specify your LDAP password in the
DefAdminPwd
property.
Uncomment and specify your organization LDAP details:
authtype = ldap
ldapURL = ldap://ldapserver:389
usersearchbase = ou=people,o=org
rolesearchbase = ou=groups,o=org
useridkey = uid
rolename = cn
rolesearch = uniqueMember
Restart the Tomcat service to log in as an LDAP user.
The following table lists the properties stored in the <context-name>_server.properties file:
Property Name
Description
Property Value
Required (Yes/No)
DatabaseType
Specifies the database used
(supported types are oracle/access/sql)
oracle/access/sql (access by default)
Yes
DSN
If oracle or sql database, specifies the
dsn used to connect to database
DSN name
required for Oracle and SQL databases
authtype
Specifies the authentication
mechanism used.
db/ldap
yes
ldapURL
LDAP server URL
URL of LDAP Server of the organization
if authtype is ldap
usersearchbase
User search base
URL of LDAP Server of the organization
if authtype is ldap
rolesearchbase
Role search base
Subcontext in LDAP server in which
role information is stored
if authtype is ldap
useridkey
User ID key which stores the User ID in
the LDAP server
user ID key
if authtype is ldap
rolename
Role Name key which stores the role
name in the LDAP Server
role name key
if authtype is ldap
rolesearch
Attribute to be searched in the role
name
role attribute name
if authtype is ldap
DefAdminUID
When server is started for the first time,
server is not connected to the
database. Therefore, access
permissions for a given user cannot be
verified. Provide a default user ID
which has the admin rights and can
access the web admin.
User ID which has admin access to
RoboHelp Server by default.
yes