Skip to content

Configure Content Security Policy (CSP) properly #416

Description

@maltesander

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 #415 is setting TALISMAN_ENABLED to false to keep existing functionality.
This should however be configured properly via TALISMAN_CONFIG to increase security.

See: apache/superset#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.

Activity

  1. changed the title [-]Configure CSP properly[/-] [+]Configure Content Security Policy (CSP) properly[/+] on Oct 19, 2023
  2. added theissue type on Apr 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions