Cookie policy banner hardcodes 2U/edX in a number of places

[kdmccormick]

Reproduction

Try to log in via the Authn MFE in Olive. The top of the page shows an edX cookie banner (try private/incognito if you don't see it):

Issues

From https://github.com/openedx/frontend-component-cookie-policy-banner:

return `edX and its Members use cookies and other tracking technologies for performance, analytics, and marketing ...`

const linkOpen = '<a href="https://edx.org/es/edx-privacy-policy" class="policy-link" target = "_blank">';

.edx-cookie-banner { .... }

Additionally, its package.json requres @edx/brand-edx.org.

Finally, these strings definitely aren't internationalized the way MFE strings usually are: https://github.com/openedx/frontend-component-cookie-policy-banner/blob/master/src/constants.js

Acceptance Criteria

1. For all strings and links, the value in this repository is either:
   • something that would work for any Open edX deployment OR
   • a null/placeholder value, indicating that there's no reasonable default.
2. SCSS classes and variables do not contain edx.
3. The @edx/brand-openedx package is installed instead of @edx/brand-edx.org.
4. The strings are internationalized using the standard method OR a follow-up issue is created to handle that.

To achieve (1) without disrupting edx.org, 2U would create its own frontend-component-cookie-policy-banner-edx repository to override this one, much like frontend-component-header-edx overrides frontend-component-header.

[kdmccormick]

@arbrandes Here's one for FWG's backlog.

[dyudyunov]

hardcoded instances (e.g. edx stage, edx prod) are also worth mentioning

[arbrandes]

@kdmccormick, the banner part of this issue had been brought up before during the Olive release cycle. It was "solved" (admittedly not ideally) via a configuration option (ENABLE_COOKIE_POLICY_BANNER) that can be used to disable the banner entirely.

Which is to say, the acceptance criteria here can remain as stated, as far as I'm concerned.

@dyudyunov, since you seem to be working on this anyway, would you like to be assigned the issue?

[dyudyunov]

@kdmccormick, the banner part of this issue had been brought up before during the Olive release cycle. It was "solved" (admittedly not ideally) via a configuration option (ENABLE_COOKIE_POLICY_BANNER) that can be used to disable the banner entirely.

Which is to say, the acceptance criteria here can remain as stated, as far as I'm concerned.

@dyudyunov, since you seem to be working on this anyway, would you like to be assigned the issue?

Yeah, I would like to help here

I was thinking about several layers for configuration of the text and behavior of the component:

• through the env vars (as embedded in the MFE)
• through the props (as the standalone component in the legacy frontend)
• defaults are TBD (e.g. "Your Platform Name Here" for the PLATFORM_NAME as it is used in the edx-plaform)

I would also like to know if there is an issue or ticket for adding the banner component in the Header component to reuse it across all the MFE pages.

Can you also provide a fork repo URL @kdmccormick mentioned in the description:

2U would create its own frontend-component-cookie-policy-banner-edx

[arbrandes]

@dyudyunov

I would also like to know if there is an issue or ticket for adding the banner component in the Header component to reuse it across all the MFE pages.

I don't think we have a specific issue for that, yet.

[dyudyunov]

@arbrandes @kdmccormick
Hi!

Are there any updates for this? I think creating an openedx fork for the component is enough for the work to start.
Please ping me when it will be ready and assign for the issue)

It would be great to create issues/tasks for the following:

Update the competent configuration logic:

I was thinking about several layers for the configuration of the text and behavior of the component:

• through the env vars (as embedded in the MFE)
• through the props (as the standalone component in the legacy frontend)
• defaults are TBD (e.g. "Your Platform Name Here" for the PLATFORM_NAME as it is used in the edx-plaform)

Include the component to the MFE Header to make it globally available:

I would also like to know if there is an issue or ticket for adding the banner component in the Header component to reuse it across all the MFE pages.

Maybe I should create a discussion post first?