Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation on SSO and Teleport Cloud does not work to edit CAP resource #11840

Closed
pschisa opened this issue Apr 8, 2022 · 0 comments · Fixed by #12544
Closed

Documentation on SSO and Teleport Cloud does not work to edit CAP resource #11840

pschisa opened this issue Apr 8, 2022 · 0 comments · Fixed by #12544
Assignees
@ptgott
Labels
bug c-og Internal Customer Reference documentation
Milestone
Docs sprint: May ...

Comments

@pschisa
Copy link
Contributor

pschisa commented Apr 8, 2022

Details

The following documentation does not work for Teleport cloud users: https://goteleport.com/docs/enterprise/sso/okta/?scope=cloud#enable-default-saml-authentication

Since the Teleport cloud CAP resource already exists in Teleport cloud, the mentioned documentation does not actually apply the resource. It only works if all metadata information from the current CAP resource is also included.

My recommendation for cloud users would be to run tctl get cap > cap.yaml and edit this file directly as this works consistently
@pschisa pschisa added documentation c-og Internal Customer Reference bug labels Apr 8, 2022
@ptgott ptgott self-assigned this May 10, 2022
ptgott added a commit that referenced this issue May 10, 2022
@ptgott
Flesh out CAP instructions
3ecba41 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
@ptgott ptgott mentioned this issue May 10, 2022
Merged
ptgott added a commit that referenced this issue May 24, 2022
@ptgott
Flesh out CAP instructions
ab369df 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 1, 2022
@ptgott
Flesh out CAP instructions
7d33614 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 1, 2022
@ptgott
Flesh out CAP instructions (#12544)
8a51270 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 2, 2022
@ptgott
Flesh out CAP instructions
55206cc 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 2, 2022
@ptgott
Flesh out CAP instructions
6c4ee52 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 3, 2022
@ptgott
Flesh out CAP instructions
2089c87 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 3, 2022
@ptgott
Backport #12544 to branch/v9 (#13110)
1fc9c42 
* Flesh out CAP instructions

Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.

* Respond to PR feedback
ptgott added a commit that referenced this issue Jun 3, 2022
@ptgott
Flesh out CAP instructions
0ce0399 
Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.
ptgott added a commit that referenced this issue Jun 3, 2022
@ptgott
Backport #12544 to branch/v8 (#13111)
1a47aa3 
* Flesh out CAP instructions

Closes #11840

Since Cloud accounts begin with a cluster_auth_preference resource,
you need to obtain your current resource via tctl get and make changes,
rather than creating a fresh one. This changes Cloud instructions in
several guides to reflect this.

Also use the same instructions for self-hosted users. If a CAP does
not exist on the backend, the shell redirection used in the
"tctl get" command will result in an empty file, which follows the
existing instructions with minimal changes.

Also update the instructions related to u2f in the Reducing the
Blast Radius guide.

* Respond to PR feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ptgott ptgott

Labels
bug c-og Internal Customer Reference documentation
Projects
None yet
Milestone
Docs sprint: May 9, 2022 – May 20, 2022
Development

Successfully merging a pull request may close this issue.

Flesh out CAP instructions gravitational/teleport
2 participants
@ptgott @pschisa