Skip to content

Investigate cluster auth conflict in uldev #290

@ajkiessl

Description

We'll want to work with the DevOps team on this.

Around the time this commit (eadf1ca) was merged to main and deployed to the uldev cluster, we started seeing requests to the GUI hang and fail with a 500 ISE. The requests never seemed to make it to the app, and the error was returned by nginx. The API endpoints (not behind cluster auth) were unaffected. We added this code (883c316) thinking we needed to configure the redirect urls from some of the headers being passed by the ingress controller. That didn't seem to work. We finally just removed the cluster auth to get it to work, but this is not ideal.

Investigate this issue and find a way to get our auth to work with the cluster auth.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions