Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Design login command #30

Open
iancoffey opened this issue Jul 6, 2021 · 0 comments
Open

Design login command #30

iancoffey opened this issue Jul 6, 2021 · 0 comments
Assignees
Milestone

Comments

@iancoffey
Copy link
Contributor

Review the design of the login plugin

Collated Context

Context from 2021-01-29 17:51:04
User: timothysc
At minimum we should have a plan in place.

Context from 2021-02-17 15:28:45
User: mattmoyer
Some issues to consider in this design:

  • How do we bootstrap trust into a management cluster where I don't have the self-signed CA bundle yet? This is very similar to the boostrapping problem in kubeadm join, and I think we could use a similar approach to kubeadm

  • How do we express "login to SaaS" and "login to TKG" in the least confusing way? Can we unify the "login to SaaS" flow across multiple CSP-based services (TMC + TSM)?

I'm sure there are a bunch more things to consider, this is just some rough notes after discussions yesterday.

@vuil vuil added the area/auth label Oct 18, 2021
@ankeesler ankeesler added this to the Icebox milestone Oct 19, 2021
@ankeesler ankeesler added area/iam Related to identity access management and removed area/auth labels Mar 24, 2022
@saji-pivotal saji-pivotal reopened this Aug 4, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

5 participants