Feature Request: Authenticating with the service account about skooner

[herbrandson]

I just want to make sure I understand. The request is that if k8dash is running with a serviceAccount, that it just use that account for all api requests and not require the user to login? Is that correct?

[spali]

Not the same usecase, because I don't use a service account. But may still the same problem.
I use a ingress proxy which does the whole oidc authentication and injects the Authorization header with the Bearer which can authenticate against the api server. The same works for all other services I have including the kubernetes-dashboard.
But k8dash asks still for the token even it logs Authorization header found. Passing through to client.
If I just enter garbage text in the token field and press enter I can enter k8dash and it shows everything that the authorized user should see.
I can repeat that by deleting the authToken in the browser local storage.
So it seems for me that as long as there is no authToken, even a token is provided in the header, it asks anyway for the token.

So in my case, the workaround is to just set the authToken in local storage to just something random.
Side note: local storage is generally not considered to be a secure place to store tokens.

[cnwaldron]

I ran into this same issue. When I use this method the "Profile" link shows "There was an error and this content was unable to display". I would expect that to be loaded and pulled from the Authorization header being used but it appears to be using the authToken in the browser local storage as previously stated.