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 THISThe organization identifier.
*''access_levels'': This section deals with providing access privileges to users based on their position within the organization. Also It 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 may have multiple <level> nodes.
***'''value''': Integer. The lower this number, the fewer privileges the users at this level have. Each <level> node must have a distinct <value>.
***''position'': Describes a combination of one role with one or more titles. For example, the Employee role could include Support Staff, Maintenance Staff, and Security as titles. <Position> nodes within <level> nodes allow the system administrator to give various kinds of Employee different access levels if needed, and also share access levels between multiple roles. A <level> node can have multiple <position> 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.
**access level hierarchy: Blacklist > Whitelist > Role&Title > Role > Default
**''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.
