Dashboard: Microsoft Edge - dashboard sign in

[grahamehorner]

running the dashboard using kubectl and accessing via Micrsoft Edge using a token fails to sign in.
using the same setup and token sign in is successful using Google Chrome

[xishian]

Same with you, but even worse when I try to login with token, nothing happened, it's still login page!

[smiklosovic]

Same as @xishian, it just does not do anything. With Firefox too. Google does not work in my case.

[smiklosovic]

@floreks what that could be?

[grahamehorner]

I've reinstalled everything onto a refresh VM and it look as if IE Edge isn't submitting the token to the service for validation; the developer tools don't seem to be showing any errors and fiddler is not seeing any https get/post action out bound?

[grahamehorner]

correction:- IE Edge is showing the following errors in debug

HTTP401: DENIED - The requested resource requires user authentication.
(XHR)GET - http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/api/v1/settings/global

HTTP401: DENIED - The requested resource requires user authentication.
(XHR)GET - http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/api/v1/rbac/status

Error during global settings reload: [object Object]

Possibly unhandled rejection: {"data":"MSG_LOGIN_UNAUTHORIZED_ERROR\n","status":401,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"api/v1/rbac/status","headers":{"Accept":"application/json, text/plain, /"}},"statusText":"Unauthorized","xhrStatus":"complete","resource":{}}

[smiklosovic]

In my case it was about roles. You are probably having them wrong.

Start it in such way there is skip button. Then if you are in, you will have the most probably some warnings there. You have to resolve them. After that you can login with token and disable skip.

I think I used Helm chart + flags, no the official apply file. That worked well (but I had to setup roles and so on afterwards anyway)

[grahamehorner]

@smiklosovic I'm not sure what your attempting to describe as I' new to kubernetes and I'm simply following the documented process on the repo; also unsure if this is a role issue as the same setup works using the Google Chrome browser for myself? note the errors occure in IE Edge prior to sign in with a token; but no errors occur in google chrome.

[maciaszczykm]

Two things:

1. Please try to verify it again with v2.0.0-beta1 as the frontend was completely rewritten.
2. Don't use Edge :)

/close

[k8s-ci-robot]

@maciaszczykm: Closing this issue.

In response to this:

Two things:

1. Please try to verify it again with v2.0.0-beta1 as the frontend was completely rewritten.
2. Don't use Edge :)

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[grahamehorner]

@maciaszczykm this issue still exists and is present when using Edge and Internet Explorer; IMHO forcing user to use/install a given browser is not a solution. Please re-open this ticket/issue, I'm happy to assist in trying to identify the root cause and resolve.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[maciaszczykm]

/lifecycle frozen

[Cellebyte]

Still broken with v2.0.0-rc.5 I was confused it only works with Chromium/Chrome.
Firefox is not working at all.

Recreated the bug with a Token.
Paste it in the input field click login. The Server is returning a 200 but the SPA is not responding with a redirect.
The user thinks nothing happened.

[shu-mutou]

Microsoft Edge 44.18362.449.0 can login to dashboard.

[Cellebyte]

Microsoft Edge 44.18362.449.0 can login to dashboard.

Correct because it is Chromium,
Firefox is still broken.

[shu-mutou]

Yes. This issue titled about MS Edge. Issue for firefox subscribed in #4922.

[floreks]

Closing this one in favor of #4922

/close