AC-75 and AC-73

Credentials Feature changes reverted in release

Render CMS course listing Using CourseSummary for user with org access role

ECOM-3419

Add logging when user is removed from exception list

ECOM-3281

ECOM-3278

ECOM-3015

ECOM-3033

ECOM-3057

Resolved ccx-keys dependency on edx-opaque-keys

Update translations (autogenerated message)

New version uses edx-opaque-keys instead of opaque-keys.

Using edx-opaque-keys instead of opaque-keys

Track push notification activity in analytics

ccx-keys has been updated to use the edx-opaque-keys library from PyPI, rather than simply expect the package to be pre-installed. The edx-opaque-keys version has been bumped as it was updated to export test packages needed by ccx-keys.

Hotfix for MA-1981 and safe sessions

When a course is updated, track whether or not a push notification is
sent.

Hotfix for MA-1981 and safe sessions

CCX REST APIs

Ignore node_modules when checking Python quality

Enroll already-existing user to a course via management command.

Our current sandbox provisioning uses a create_user management command,
which creates and enrolls a user into a course. However, for TE-1128, we
will need a way to enroll the same user to multiple courses (which are
dynamic at time of provisioning). Using the existing management
command is no longer feasible for that, so we are using one that accesses
the enrollment API, which is the new standard for new enrollment capabilities.

CCX REST APIs
OAUTH2 authorization for CCX APIs
- oauth2 authorization required for ccx list.
- Course-instructor permission for ccx api endpoint
- Protection for detail view too.

Tests for CCX REST APIs and OAUTH2 authorization

Update age calculation to be more conservative.

Fix file upload in IE

PHX-241 Upgrade xblock_lti_consumer

Add the basis of configuring a cache TTL for course assets.

ECOM-3525

Add latest edx-organization version in the platform

Specific user cannot access studio.edge.edx.org/home

Installing edx-opaque-keys from PyPI

This introduces a mechanism to control the time-to-live for an unlocked
course asset, which will allow browsers and intermediate proxies/caches
to cache these course assets, determinstically.

Locked assets, with their nature of requiring authorization, are not
eligible for caching.