Support passing bearer token in header about skooner

[herbrandson]

Thanks for the request @tsjnsn. I have some ideas about how to implement this, but want to make sure I understand you correctly first. Could you explain a bit more about your use case?

[tsjnsn]

Basically I want to do the authentication at a different layer. My case is I have a proxy in front of k8dash that handles authentication (not OIDC based), and it would add the authorization header after that for all requests to k8dash.

…

On Mon, Jun 17, 2019 at 9:59 PM Eric Herbrandson ***@***.***> wrote: Thanks for the request @tsjnsn <https://github.com/tsjnsn>. I have some ideas about how to implement this, but want to make sure I understand you correctly first. Could you explain a bit more about your use case? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATQ7IF7IKLSTT2ADXAFEPTP3BFS3ANCNFSM4HY2DCWA> .

[herbrandson]

Gotcha. One more quick question. If there were already a token set in the browser and a new request came in w/ a different token, it sounds like you'd want the new token to overwrite the existing one, correct?

[herbrandson]

Hey @tsjnsn. I've just pushed an update to the :dev docker label which should resolve this issue. Would you mind testing and verifying that it works for your use case?

[tsjnsn]

It doesn't seem to be working for me. For testing, I'm using Requestly to set the Authorization header to my Bearer token, then navigating to the site. it's still prompting me for an authorization token though

[tsjnsn]

Gotcha. One more quick question. If there were already a token set in the browser and a new request came in w/ a different token, it sounds like you'd want the new token to overwrite the existing one, correct?

I'm not sure, but I think I would expect the browser's token to take precedence.

[herbrandson]

Sorry about that. I'm not sure what's going on there. Can you attache the server logs for that request?

[herbrandson]

Hey @tsjnsn. I just wanted to follow up quick. Were you able to make any progress on this?

[herbrandson]

@tsjnsn This was working in my tests. I'm closing for now, but please reopen if I can help track down your issue. Thx!

[djsly]

Hello, the latest release is broken, when you don't have a token, the logout function loops with the login function.

We have to revert back to the version of 21days ago to have the k8dash to work again.

[zhixiangjoy]

Hello, the latest release is broken, when you don't have a token, the logout function loops with the login function.

We have to revert back to the version of 21days ago to have the k8dash to work again.

I have the same probelem,when I click LOGOUT, k8dash will return auto login(use keycloak),this make logout doesn't work.This make me confused,What could I do to change this. Thinks!

[herbrandson]

@zhixiangjoy This issue was resolved some time ago. Can you verify you're on the latest version?