Content Controller user accounts are now divided into two groups: administrators, who have all the same capabilities of pre-2.1 users, and regular users, who no longer have access to user and application management features. Regular users are also subject to the new account access controls described below.
Account Access Controls
Each account now has a list of users who have access to that account's data. Users with read-only access can view the account, its content, and its usage and reporting data. Users with read-write access can also add and remove content from the account, and change its settings. Administrators have full access to all accounts.
Share as LTI
In addition to SCORM 1.2, SCORM 2004 3rd Edition, and AICC, you can now share content from accounts as an LTI tool provider. Instead of downloading a ZIP package, you'll get a launch link, key, and secret that can be used to launch the content from an LTI-capable LMS.
You can now look up player debug logs, launch history, and the complete registration state for a particular learner and course, to help troubleshoot content and LMS issues.
- Add course configuration to the public automation API.
- Administrators can lock user accounts to prevent them from signing in.
- Customize the player stylesheet per account.
- Stricter invalidation of user auth tokens after signing out, changing passwords, etc.
- Whitelist and blacklist for MIME types in uploaded courses.
- Add a configuration setting to disable sign-in page customization.
- Change HTTP status of public automation API account imports when the content has already been added to the account from 500 to 409.
- Display public automation API endpoint URL and status in Applications list.
- Include an "unsubscribe" link in license alert emails.
- Prevent user-set and auto-generated course version IDs from colliding.
- Remove unsupported Internet Explorer versions from the IE Compatibility Mode course setting list.
- Sanitize HTML in account error messages.
- Show the launch number in the learner interaction report, to help distinguish between "duplicate" interactions.
- Updating a course's metadata now changes the course's modified date.
- Delete a course's preview links when the course is deleted.
- Ensure that course name changes are reflected in the course player UI.
- Fix sorting of accounts by last activity or modification dates.
- Fix sorting of previews by modification date.
- Use "cmi5" instead of "Unknown" in the error message about switching learning standards between course versions.
Notes for Self-hosted Installations
Ansible 2.4 / Playbook Changes
Your Ansible installation will need to be updated to >= 188.8.131.52 to run these playbooks.
We have removed the
monit role. If you are using a custom env.yml to run your playbooks, you may remove this role from the list. The health check daemon functionality was moved to the
content-controller role, and monit is no longer installed as a dependency.
MySQL 5.7 Databases
MySQL 5.7 is now supported for remote and local databases. For the foreseeable future, we will continue to support MySQL 5.6. Local MySQL databases will be updated to the latest release of MySQL 5.7. If you have applied any custom configuration to your local MySQL instance, then you will need to re-apply these changes. This does not apply to installations hosting MySQL on a separate machine from the application.
Ubuntu 16.04 LTS
We do not recommend updating an existing server from Ubuntu 14.04 to Ubuntu 16.04. Instead, it is best to start with a blank Ubuntu 16 install.