Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to skip login by adding Authorization header #8760

Closed
csuich2 opened this issue Mar 7, 2024 · 3 comments · Fixed by #8762
Closed

Unable to skip login by adding Authorization header #8760

csuich2 opened this issue Mar 7, 2024 · 3 comments · Fixed by #8762
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@csuich2
Copy link

csuich2 commented Mar 7, 2024

What happened?

After upgrading to v7.0.0 I'm trying to adapt to the removal of the --enable-skip-login page. I did this as indicated in the docs by having our proxy add the Authorization header however I'm still presented with the login page.

The docs also indicate:

IMPORTANT: Authorization header will not work if Dashboard is accessed through API server proxy. kubectl port-forward described in Accessing Dashboard guide will not work. It is due to the fact that once request reaches API server all additional headers are dropped.

however it isn't clear if that also applies to the Kong gateway.

Update: I tried removing the Kong gateway from the equation by having our proxy forward /api requests to the api service and all other requests to the web service but am still seeing the login page.

What did you expect to happen?

With the Authorization header present the login page should not be presented.

How can we reproduce it (as minimally and precisely as possible)?

Use Requestly as described in the docs to add the header when loading the dashboard.

Anything else we need to know?

No response

What browsers are you seeing the problem on?

Chrome, Microsoft Edge, Firefox

Kubernetes Dashboard version

v7.0.0

Kubernetes version

v1.27.3

Dev environment

No response

@csuich2 csuich2 added the kind/bug Categorizes issue or PR as related to a bug. label Mar 7, 2024
@floreks floreks added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 7, 2024
@csuich2
Copy link
Author

csuich2 commented Mar 7, 2024

Woah - thanks for the quick turnaround!

I've upgraded my chart to 7.1.1 but unfortunately I'm still experiencing the same behavior. Do you have any suggestions on how to debug further to ensure this isn't a problem with my setup? AFAICT I'm properly setting the Authorization header. Can you confirm that the Kong gateway doesn't strip this header?

@csuich2
Copy link
Author

csuich2 commented Mar 7, 2024

Oops! Turns out I just needed to bounce the Kong Proxy pod since it didn't recreate after the ConfigMap change.

Thanks again for the super quick fix!!!

@floreks
Copy link
Member

floreks commented Mar 8, 2024

Oops! Turns out I just needed to bounce the Kong Proxy pod since it didn't recreate after the ConfigMap change.

Thanks again for the super quick fix!!!

Not sure if we can automate restart on change since this is a subchart but I will take a look. I will add a note to the release notes though.

Great that it works for you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants