* dont allow disabling second factor
* update docs for 2fa change
* add environmental variable to work around disabled 2fa
* check if its cloud
* update todos
* add a test
* introduce insecure test mode
* fixes for tests
* [docs] Update DB access AWS IAM reference page
* add other aws databases
* reword and fix a few spots
* remove please and add the for service
* address review coments
* fix spelling
* fix link
* Remove auto-discovery from specific DB guides
Closes#22942
Help users enroll specific databases with Teleport while directing them
auto-discovery instructions if they want to go that route.
- Revert #30913 for guides to enrolling specific databases. For guides
that always included auto-discovery instructions, add instructions to
enroll databases at specific URLs.
- Add a note in the introduction sections of AWS guides that it is
possible to enroll AWS databases with auto-discovery, linking to the
relevant guide.
* Respond to greedy52 feedback
- Remove auto-discovery notes where they are incorrect.
- Remove unneeded `id` flags.
- Use `teleport db configure create` for Redshift Serverless, removing
unneeded config fields. Also add the `aws-bootstrap.mdx` partial to
the Redshift Serverless guide, making it more consistent with other
guides that include `teleport db configure bootstrap` instructions.
- Minor spelling/grammar tweaks.
- Fix example description outputs.
- Use URI/protocol flags in `rds-proxy.mdx` instructions.
- Restore `opensearch` to `database-config.yaml`.
* Respond to greedy52 feedback
- Add the `--name` parameter to `db configure create`
- Edit `tsh db ls` output in the RDS guide
* Fix linter issues
* Replace audit_retention_period with retention_period
* Override a zero retention period with the default value
* Update docs to reflect which backends respect the retention_period
* Remove unused json tags from dynamo events config
---------
Co-authored-by: Musaed Albrikan <mabrikan@gmail.com>
We should not use `[true|false]` syntax when describing fields
in a YAML file, as the square brackets may be interpreted as a
YAML list instead of a scalar boolean value.
* Change Open source and OSS to Teleport Community Edition
* Change open-source to Teleport Community Edition
* Role access requests in the nav and title
* Add more details about specifying a CA pin
Closes#9946
The CA pin is the only Teleport configuration field where we have not
yet documented the possibility of specifying a value using a file path.
This change includes this information, as well as the (also
undocumented) fact that you can specify a list of CA pins. Also updates
the docs path that the CA pin reference links to.
* Respond to zmb3 feedback
* Respond to lsgunn-teleport feedback
* Use teleport.example.com as the example proxy
* Add the core Jamf guide steps
* Add sync schedule optional section
* Add the multiple sources optional section
* Add the auto-enrollment guide
* Add the Jamf service reference config
* Add words to cspell.json and sort it
* Use `--config` instead of `-c`
* Apply Alex's suggestions
* Add preview admonition to auto-enrollment.mdx
* Add scopes for auto-enrollment guide
* Add scopes for jamf-integration guide
* Remove "and restart" from Auth update instructions
* Auth restart instructions
* s/Jamf service/The Teleport Jamf service/
* Use an inline code block for external links
* s/the following/the following keys/
* Use inline code block for key names
* Use inline code block for key names
* Use inline code block for key names
* Use inline code block for key names
* Mention "local workstation" after we transition from Jamf to Teleport
* Mention Jamf service host when switching context
* Use `(=presets.tokens.second=)`
* Use `(=presets.ca_pin=)`
* Mention logs example explicitly
* Add a missing comma
Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
* Address Alex's comments
* Reflow text
* Remove redudant tsh prereqs sentence
* Add a registered device to auto-enrollment prereqs
* Use headers instead of bold
* Use a narrower image for jamf-setup-2.png
---------
Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
* Okta documentation.
Okta documentation has been added for the Okta service. This aims to explain
the Okta service and give simple examples.
* Typo fixes, comment fixes, naming fixes.
* Reorganization of Okta docs, fixing typos, adding in images and tuning wording.
* Use an architecture image for now until mermaid support can be reenabled.
* Correct spellings.
* Update docs/pages/application-access/okta/guide.mdx
Co-authored-by: Roman Tkachenko <roman@goteleport.com>
* Correct architecture diagram.
* Linting fixes.
---------
Co-authored-by: Roman Tkachenko <roman@goteleport.com>
In gravitational/docs#238, we will add a linter that lints for incorrect
usage of Teleport terms. This change fixes linter violations to
anticipate this new linter.
Changes include:
- Ensuring that Teleport service names are capitalized
- No longer using the "[Resource] Access" terminology. Instead, talk
about adding resources, using Teleport services, etc.
The desktop listen address is for the proxy to be able to connect. If it's set to localhost/127.0.0.01 then a Proxy can't reach it. This makes it more in-line with SSH listener.
* SAML identity provider docs.
SAML IdP documentation has been added.
* formatting
* spelling
* Zac's and Roman's feedback.
* Valid config.json.
* Linting updates.
* usr Var component
Adding as a unique commit in case it's not desired
* align output with object name
* Roman's feedback, add in a section for disabling the IdP.
* copy edits
* SAML Grafana guide (#22545)
* init Grafana SAML guide
* respond to review feedback
* Correct entity provider to identity provider.
* Note that HSM is not currently supported.
* Fix link.
---------
Co-authored-by: alexfornuto <alex.fornuto@goteleport.com>
* Reorganize the config reference
Closes#11253
This change breaks up the config reference by moving each Teleport
service's configuration settings into a separate YAML snippet, and
organizing each YAML snippet into a `TabItem` within a `Tabs` with
`dropdownView` enabled. When Teleport Enterprise Cloud doesn't support a
service, this change adds a `Notice` with a message about Teleport
Enterprise Cloud in the relevant `TabItem`.
I thought this approach would be cleaner than alternatives:
- **Including an H2 for each service:** With this approach, the
configuration reference would be even longer than it is now. With the
approach I'm proposing, readers would navigate to "Reference
configurations", then choose a service from a dropdown menu: much less
scrolling for slightly more clicking.
- **Including another set of `TabItem`s for Teleport editions:** I
thought about adding a `Tabs` with a dropdown option for each Teleport
edition and a horizontal `TabItem` for each service, but this would
require horizontal scrolling and doesn't scale very well.
- **Including horizontal tabs for each Teleport edition**, with an inner
dropdown menu for each Teleport service: There is currently no way to
do this without multiple `Tabs` components, which gets messy quickly.
**Note** that this change does not attempt to copy-edit comments/example
values within the configuration snippets. The scope of this change is
limited only to reorganization.
* Respond to PR feedback
* Update docs/pages/includes/config-reference/instance-wide.yaml
Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
* Respond to PR feedback
Use headings instead of `TabItem`s to split up sections of the config
reference.
---------
Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
Alex McGrath