Update SSO guides to take into account new commands: tctl sso test, tctl sso configure.#12941
Update SSO guides to take into account new commands: tctl sso test, tctl sso configure.#12941Tener wants to merge 42 commits into
tctl sso test, tctl sso configure.#12941Conversation
377dee1 to
221b96a
Compare
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Edit the SSO introduction: - Add examples of all connectors so users don't need to find them in the examples directory - Add subheadings to the "Configuring SSO" section for clarity - Minor grammar/style edits Specific SSO guides: - Use the commercial-prereqs-tabs partial in Prerequisites sections, since this partial already exists, rather than ent-user-prereqs.mdx. This partial is more specific about requiring a running Teleport cluster, and links to the Getting Started guide for the Enterprise edition. - Minor tweaks to the scoped information shown in the samlauthentication.mdx and oidcauthentication.mdx partials - Restored the original wording of edition-prereqs-tabs.mdx, which is more specific about how to get started with a running Teleport cluster on different editions, and includes instructions for tsh.
ptgott
left a comment
There was a problem hiding this comment.
I've left a partial review. I need to continue reviewing at the top of the new "Step 3/5. Test the connector" section.
|
|
||
| The values of `client_id`, `client_secret`, and `redirect_url` come from the | ||
| GitHub OAuth App you created earlier. | ||
| The values of `client_id`, `client_secret` come from the GitHub OAuth App you created earlier. `redirect_url` is automatically configured by [`tctl sso configure github`](../reference/cli.mdx#tctl-sso-configure-github) based on the settings of Teleport cluster. |
There was a problem hiding this comment.
| The values of `client_id`, `client_secret` come from the GitHub OAuth App you created earlier. `redirect_url` is automatically configured by [`tctl sso configure github`](../reference/cli.mdx#tctl-sso-configure-github) based on the settings of Teleport cluster. | |
| The values of `client_id` and `client_secret` come from the GitHub OAuth App you created earlier. `redirect_url` was automatically configured based on the settings of your Teleport cluster when you ran `tctl sso configure github`. |
To connect the tctl command to the earlier step in this section. Also, I think we can remove the inline link to avoid breaking the reader's focus (https://goteleport.com/docs/contributing/documentation/style-guide/#expectations-1).
There was a problem hiding this comment.
Thank you for the improved phrasing.
I'm not sure if including the link constitutes the breaking of reader focus: we are not forcing them to follow the link, but rather making an option to do so if they are interested. This is similar to inline-link style in Wikipedia, for example:
== Architecture ==
Teleport is written in Go programming language, and runs on UNIX-compatible operating systems, including Linux, macOS, and several BSD/OS variants. Teleport consists of two executables:
tsh(command line client) andteleport(server daemon).
Let me know what you think, though.
f410f8b to
f295584
Compare
|
@ptgott I have rebased this PR on top of another, so this is tagged as "Outdated" #12941 (comment), but this is definitely still relevant. Hoping to hear your thoughts on this. |
tctl sso test, tctl sso configure.tctl sso test, tctl sso configure.
|
@Tener Thanks for working on this! Let me know when all guides have been added, and I'll carve out time to give this PR a complete review. |
|
@Tener Also, would it be feasible to split this into multiple PRs, either one per guide or one per ≈250-500 lines of changes? This will make it a lot easier for me to review. We can also can get completed guides merged while others are waiting to be finished. |
No problem, I can split it. I'm waiting for #12407 to be merged before I continue the work on this one. |
|
Closing in favor of more granular PRs. |
Planned scope of this PR:
CLI reference forMoved to PR: CLI ref fortctl sso test,tctl sso configure.tctl ssocommands. #13148Parent: #9270