stackabletech / stackabletech/superset-operator
Configure Content Security Policy (CSP) properly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Description
From superset version 3.0.0 the TALISMAN_ENABLED defaults to true. This leads to not being able to login from external sources. The PR https://github.com/stackabletech/superset-operator/pull/415 is setting TALISMAN_ENABLED to false to keep existing functionality.
This should however be configured properly via TALISMAN_CONFIG to increase security.
See: https://github.com/apache/superset/pull/24262
See: https://superset.apache.org/docs/security/#content-security-policy-csp
Issue checklist
- Describe the use-case, as far is possible. For instance, using the pattern "As a XXXX, I would like XXXX to be able to do XXXX" helps to identify the feature as well as the problem it is intended to address.
- Indicate an approximate level of importance and urgency.
- Indicate if there is a known work-around until such time as the issue has been implemented.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the configuration handled by the Superset operator and the workaround in pull request #415, then read the linked Apache Superset CSP documentation and pull request. Done means TALISMAN_CONFIG is configured so external login continues to work while CSP protection is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100