Dashboard: Login improvements

Created on 11 Sep 2017  路  13Comments  路  Source: kubernetes/dashboard

Tracking issue for further non-critical login improvements.

  • [x] Allow overriding key holder name/namespace with arguments passed to dashboard. This will allow multiple dashboard deployments to use different encryption keys.
  • [ ] Token blacklisting feature
    In case user logs out his token should be invalidated. We should blacklist it until it expires.
  • [ ] Key rotation feature
  • [ ] Consider generating self-signed certificates signed by apiserver CA. This would allow to keep HTTPS enabled by default.
  • [ ] Support for external identity providers (i.e. Github OAuth, OIDC). #2621, #2630
  • [ ] Improve error handling and localize all errors.
  • [ ] https://github.com/kubernetes/dashboard/issues/964#issuecomment-332842897
  • [ ] Allow logging in when a very long token is provided (i.e. Azure with groups, etc.)
kinfeature lifecyclfrozen prioritcritical-urgent

Most helpful comment

It would be absolutely fantastic if we could get some traction on this.

All 13 comments

It would be nice when I login with kubeconfig file to automatically show me the namespace from kubeconfig file instead of just showing default namespace by default.

Is there a ticket on the core side that tracks implementation of the API features/endpoints required for OIDC to work sensibly in dashboard?

I haven't been following core roadmap lately, so I don't know. We'll try to revisit it after angular migration.

What's the latest on this? I'm interested in having OIDC auth information published in the kube-public namespace for interested clients to discover, for other reasons, in addition to possibly having the dashboard auth scenario be much simpler.

It would be also awesome if, when you go to some url (for example, dashboard/#!/log/namespace/pod), and it required sign, it wouldn't forget your url and send you to the page you wanted, and not to overview of default namespace.

It would be absolutely fantastic if we could get some traction on this.

Also interested by the feature that @cohadar suggested :

It would be nice when I login with kubeconfig file to automatically show me the namespace from kubeconfig file instead of just showing default namespace by default.

Any news/info about this ?
Thanks

Is there any integration on access to the dashboard and AWS IAM?

Many thanks.

Still waiting for this...

@sshishov You can wait or you can contribute. We are not able to do everything instantly with just a few people.

Any news regarding oidc support? :)

I know this things take a long time.. any news about it ?

The main issue is that we don't have anyone willing to work on that right now. Our main focus goes to designing and creating a new standalone gRPC API for Dashboard.

Was this page helpful?
0 / 5 - 0 ratings