superset helm chart getting error 302 and redirected

[IlayBor]

iv spent the last couple of days trying to figure this out and I need some help.

Ill note that im a beginner, so I may have done some stupid stuff.

Anyways, I tried to deploy superset via helm chart.
Locally, everything worked perfectly.


Now, I tried to upload it to the cluster.
The major changes are:

1. I have actual dns now (that iv set up with ingress)
2. I have to access it via https

I can reach the dns and actually see the login page,

but once I enter my username and password I get redirected to the login page again.
(and in the network tools in chrome I can see 302 for my POST request then redirected to the GET login page)

iv added photos of that.

Also, im adding the .Values of my superset helm chart, iv honestly tried everything at this point so I have bunch of configs there.

.Values:

init:
  resources: {}
  adminUser:
    username: admin
    firstname: admin
    lastname: bi
    email: [email protected]
    password: admin

configOverrides:
  secret: |
    SECRET_KEY = 'MY-KEY'
  superset_config: |
    WEBSERVER_BASE_URL = "https://DNS.com"
    TALISMAN_ENABLED = False
    WTF_CSRF_ENABLED = False
    ENABLE_PROXY_FIX = True
    SESSION_COOKIE_SECURE = True
    DEFAULT_LOGIN_REDIRECT_URL = "/superset/welcome/"
    PREFERRED_URL_SCHEME: "https"
    WEBDRIVER_BASEURL = "https://DNS.com"

serviceAccountName: superset-sa
serviceAccount:
  create: false

image:
  repository: superset
  tag: sha-63f06a6

ingress:
  enabled: true
  ingressClassName: alb
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/healthcheck-path: /health
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/group.name: X-group
    alb.ingress.kubernetes.io/load-balancer-name: X-alb
    alb.ingress.kubernetes.io/group.order: "2"
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]'
    alb.ingress.kubernetes.io/security-groups: X-sg
    alb.ingress.kubernetes.io/manage-backend-security-group-rules: "true"
    alb.ingress.kubernetes.io/target-type: "ip"
    alb.ingress.kubernetes.io/x-forwarded-for-header: "X-Forwarded-For"
    alb.ingress.kubernetes.io/x-forwarded-proto: "https"

  hosts:
    - DNS.com
  path: /
  pathType: Prefix

bootstrapScript: |
  #!/bin/bash
  pip install \
    "clickhouse-connect>=0.6.8" \
    "psycopg2-binary>=2.9.10" \
    &&\
  if [ ! -f ~/bootstrap ]; then echo "Running Superset with uid {{ .Values.runAsUser }}" > ~/bootstrap; fi

postgresql:
  postgresqlPassword: admin
  serviceAccount:
    create: false
    name: superset-sa
  auth:
    username: admin
    password: admin
    database: postgresql

redis:
  password: admin
  serviceAccount:
    create: false
    name: superset-sa

Any help would be EXTREMLY appreciated, I feel like iv look everywhere but I can't figure this out.

[dosubot[bot]]

Hey @IlayBor! I'm here to help you with your Superset deployment using the Helm chart. Let's get to the bottom of this together.

I found two similar unsolved discussions that might be relevant to your issue:

1. Superset redirects to http from https ^[1].
2. SSL with NLB and ACM on EKS ^[2].

Regarding your configuration, here are a few points to consider:

1. ENABLE_PROXY_FIX: This setting should be True when Superset is behind a proxy, as it allows the application to correctly interpret the X-Forwarded headers. This is crucial for handling HTTPS requests properly ^[3].

2. PREFERRED_URL_SCHEME: Ensure that this is set to https to indicate that the preferred URL scheme for generating URLs is HTTPS. This helps in maintaining the HTTPS scheme throughout the application ^[3].

3. SESSION_COOKIE_SECURE: Setting this to True ensures that session cookies are only sent over HTTPS connections, which is important for security when using HTTPS ^[4].

Make sure that your ALB and ingress are correctly configured to handle HTTPS and that they are forwarding the necessary headers to Superset. Additionally, verify that your Helm chart values are correctly applied and that there are no typos or misconfigurations in your values.yaml file.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[IlayBor]

[dosubot[bot]]

A 302 redirect during the login process in Superset can occur due to several reasons, often related to misconfigurations in handling HTTPS or session management. Here are a few things to check:

1. Session Management: Ensure that your session management settings are correctly configured. The SESSION_COOKIE_SECURE setting should be True to ensure cookies are only sent over HTTPS. However, this requires that your entire setup, including the load balancer and ingress, is correctly handling HTTPS ^[1].

2. Proxy Headers: Since you're using an ALB with ingress, make sure that the X-Forwarded-Proto header is being set to "https". This is crucial for Superset to understand that the original request was made over HTTPS. You have already set ENABLE_PROXY_FIX = True, which is correct for handling these headers ^[2].

3. PREFERRED_URL_SCHEME: This should be set to https to ensure that all generated URLs use the HTTPS scheme, which you've already configured ^[2].

4. Ingress and ALB Configuration: Double-check your ingress and ALB settings to ensure they are correctly configured to handle HTTPS and forward the necessary headers to Superset.

If these configurations are correct and the issue persists, it might be helpful to look into the specific logs and configurations of your ingress and ALB to ensure they are not causing the redirect loop.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[IlayBor]

I added more info on the problem
any help would be extremely appreciated