Learners want to have the usual course navigation when viewing a wiki,
so that they can go back to the course related to the wiki and browse
other tabs/sections of the course.

Wiki reads the course from the `request.course`. If it's not present,
i.e.  None or not set on the request, it will not show the course
navigation UI.

It seems like `WikiAccessMiddleware` already has the code that parses
course id from the request (when the request is for a wiki view) and
sets the course for the request. However, it doesn't work in most
scenarios, because the course id is not in the it's normal format in
most requests that go to wiki.

For example, when a leaner clicks on a wiki tab from the course
overview, they are redirected to `/wiki/<wiki_slug>/` path. The wiki
slug is taken from course's `wiki_slug` field. This slug can be used to
figure out what course this wiki belongs to in most (not all) cases.

This commit adds code to the `WikiAccessMiddleware` that attempts to
find a course based on wiki slug, and in case of success, sets the
course to the `request.course`, so that wiki can display course
navigation UI.

…ed-roles-studio-fix

Fix studio for users with derived roles and some other related changes [BB-7834]

…penedx#33484)

Limited Staff should not have studio read access by design.

However, since many LMS views depend on the `has_course_author_access` check and `course_author_access_required`
decorator, we have to allow write access until the permissions become more granular. For example, there should
be STUDIO_VIEW_COHORTS and STUDIO_EDIT_COHORTS specifically for the cohorts endpoint, which is used to display
"Cohorts" instructor dashboard tab.

Update JWT Cookie vs Session user monitoring

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

Co-authored-by: robrap <[email protected]>

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

…dx-enterprise-52302e3

feat: Upgrade Python dependency edx-enterprise

…length_default

feat: Update the minimum password length.

enterprise version bump

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

FIXES: APER-2407

…e-edx-enterprise-7202c22

feat: Upgrade Python dependency edx-enterprise

…nality-from-edx-platform

* chore: replace pyjwkest with pyjwt

…nality-from-edx-platform

linting, fixing pr comment

Removing unused import

fix: restored badges handlers

feat: remove FE code for badges

fix: resolved failing tests

fix: removed test case for badges app

fix: unused import error

fix: Response Field Count

fix: shareable account response length

fix: resolved PR comments

fix: revert settings override

feat!: Removed Badges App

fix: restored badges handlers

feat: remove FE code for badges

fix: resolved failing tests

fix: removed test case for badges app

fix: unused import error

fix: Response Field Count

fix: shareable account response length

fix: revert subscription badge

…nedx#33535)

I get a weekly CI failure email due to this scheduled workflow running on
my fork of edx-platform. Cancelling the job when it runs on a fork prevents
this.

…31893)

feat: Account and profile MFE legacy removal - redeployment

* Revert "Revert "FC-0001: Account pages -> micro-frontend (openedx#30336)" (openedx#31888)"

This reverts commit 90c4ca6.

* refactor: removed filters test from user_api accounts

---------

Co-authored-by: Bilal Qamar <[email protected]>

…penedx#31893)" (openedx#33542)

This reverts commit 08f5e7e.

…ns/aws-actions/configure-aws-credentials-2

build(deps): bump aws-actions/configure-aws-credentials from 1 to 2

Currently, ./xmodule/ unit tests are only run with LMS settings. However,
./common/ and ./xmodule/ are run twice: once with LMS settings and once with
CMS settings.

Just like ./common/ and ./openedx/, the unit tests in ./xmodule/ validate
behavior in both LMS and CMS. So, order to fully test ./xmodule/, we should to
run its tests with CMS settings too.

This will enable us to better validate certain LibraryContentBlocks behaviors
being touched by openedx#33263 which can't
be expressed under LMS settings.

Also in this commit:

* refactor: rename the shards to be clear whether they're running under LMS or CMS
* docs: correct comments regarding conditions under which codejail's
   test_cant_do_something_forbidden is skipped.
* test: update a unit test which was using the now-deleted library_sourced block to use
   library_content block instead.

…ve-coaching-functionality-from-edx-platform

feat: remove deprecated coaching from edx-platform

…penedx#33439)

version bump

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

…edx-enterprise-db4911b

feat: Upgrade Python dependency edx-enterprise

[DEPR]: lms/djangoapps/badges

This contribution is part of the [FC-0012 project](https://openedx.atlassian.net/l/cp/XGS0iCcQ) which is sparked by the [Translation Infrastructure update OEP-58](https://open-edx-proposals.readthedocs.io/en/latest/architectural-decisions/oep-0058-arch-translations-management.html#specification).

…dx#33557)

…update_enrollment

fix: rename update cache functions to what they are

* feat: Add url that exposes taxonomy tags CRUD API

Include `content_tagging` namespace for content_tagging urls in cms
for `sub_tags_link` to work in multi-level taxonomy tags.

* chore: Bump openedx-learning version

Use Open edX as a noun on the default Open edX homepage

…-choy

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

…edx-enterprise-5009d05

feat: Upgrade Python dependency edx-enterprise

v2 is giving warnings:

```
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
```

…nedx#33166)

enterprise version bump 4.6.9

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

…e-edx-enterprise-086834a

feat: Upgrade Python dependency edx-enterprise

…3590)

This allows clients to check if a file already exist before
overwriting the asset with new data. See openedx/studio-frontend#384

the code asserts that this is a key rather than a string

TODO posits cache key is not in use, it is used in this file via signal.

…ent_clean

small cleanups in course enrollment while researching

Remind devs about backporting their bug fixes to
the Quince master branch and think about
backporting to Palm as well

…wser for karma

…enedx#33605)

…nko/additional_name_check

…penedx#33395)

… button at Instructor tab

chore: remove bok-choy settings

This repository is now managed by the Axim Collaborative and security issues
with it should be reported to [email protected] instead of [email protected]

This work is being done as a part of openedx/wg-security#16

…ove-bok-choy

Revert "chore: remove bok-choy settings"

related issue: openedx#33572

related issue: openedx#33584

note: this warning is rased from a third party library (elasticsearch)

related issue: openedx#33584

note: this warning is from a third party library (libsass)

related issue: openedx#33584

note: it has been replaced with add_custom_attribute. it is just a rename
https://docs.newrelic.com/docs/release-notes/agent-release-notes/python-release-notes/python-agent-80300/

related issue: openedx#33585

Related issue: openedx#33592

Related issue: openedx#32888

…openedx#33625)

…e-uuid-setting

feat: add enterprise customer related setting

fix: event bus producer config merging

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`

Co-authored-by: rgraber <[email protected]>

By default DRF sets 'DEFAULT_AUTHENTICATION_CLASSES' to:

```
[
    'rest_framework.authentication.SessionAuthentication',
    'rest_framework.authentication.BasicAuthentication'
]
```

We also want to allow for JWT Authentication as a valid default auth
choice.  This will allow users to send JWT tokens in the authorization
header to any existing API endpoints and access them. If any APIs have
set custom authentication classes, this will not override that.

I believe this is a fairly safe change to make since it only adds one
authentication class and does not impact authorization of any of the
endpoints that might be affected.

Note: This change changes the default for both the LMS and CMS because
`cms/envs/common.py` imports this value from the LMS.

BREAKING CHANGE: For any affected endpoint that also required the user
to be authenticated, the endpoint will now return a 401 in place of a
403 when the user is not authenticated.

- See [these DRF docs](https://github.com/encode/django-rest-framework/blob/master/docs/api-guide/authentication.md#unauthorized-and-forbidden-responses) for a deeper explanation about why this changes.

- Here is [an example endpoint](https://github.com/openedx/edx-platform/blob/b8ecfed67dc0520b8c4d95de3096b35acc083611/openedx/core/djangoapps/embargo/views.py#L20-L21) that does not override defaults and checks for IsAuthenticated.

Generally speaking, this is should not be a problem. An issue would
appear only if the caller of the endpoint is specifically handling 403s
in a way that would be missed for 401s.

When including `JwtAuthentication`, the auth_header becomes `JWT
realm="api"`. Without it, it is `None`. This changes the behavior of the
code in DRF and returns a slightly different auth response.

Relevant Code: https://github.com/encode/django-rest-framework/blob/56946fac8f29aa44ce84391f138d63c4c8a2a285/rest_framework/views.py#L456C3-L456C3