1
edit
Changes
→Components of config.xml
*''system'': System values that do not fit neatly into the other categories
**'''timeout''': Integer. After that many minutes of inactivity, a user will be logged out.
*''ldap'': Information about the organization's LDAP server
**'''url''': String. The ldap:// URL of the server itself.
**'''o''': String. PLEASE DOUBLE-CHECK THE PURPOSE OF THIS
*''ldapfields'': This section is of the most concern for LDAP portability, with the specific LDAP fields to look for during authentication.
**'''user_id''': String. The field in your organization's LDAP which denotes the user ID.
**'''user_role''': String. The field in your organization's LDAP which denotes the user's organizational role.
**'''user_title''': String. The field in your organization's LDAP which denotes the user's title.
*''access_levels'': This section deals with providing access privileges to users based on their position within the organization. Also incorporates a blacklist for banned users and a whitelist for administrators.
**''level'': This structure allows additional access levels to be created and assigned as needed. Config.xml will have multiple <level> nodes.
**''blacklist'': A list of users who are banned from the server. These users can still attend meetings which allow guests if they have been given the Guest URL.
***'''username''': String. One user's user ID to ban from the server. A <blacklist> node can contain multiple <username> nodes.
**''courseList'': A list of course codes to make available to users creating Lectures.
***'''course''': String. A course code. A <courseList> node can contain multiple <course> nodes.