There are still some hard-coded values for SSO URL in Chrome codebase: https://github.com/RedHatInsights/insights-chrome/blob/master/src/auth/platformUrl.ts#L11

We are using these as a fallback if the SSO URL is not populated by FEO. It can and should be defined in the frontend environment CRD: https://github.com/RedHatInsights/frontend-operator/blob/main/api/v1alpha1/frontendenvironment_types.go#L75 for all environments. including fedramp.

We also have to make a mapping for some "special" cases, like console.dev. It is just a stage but has a different SSO. But the frontend environment is the same as for stage and the distinction happens on Akamai level.

This will require a new attribute and a mapping which Is currently hard coded into Chrome.

We should output new operator=generated data (adding a new entry to our shared config map) and replace the embedded Chrome sooUrl config with a separate request for SSO config, which should be the first request chrome ever makes. We would replace one request for another because we are now making two calls to fed-modules.json anyway/.