* docs: explain awsic plugin install flag
* expand the use system credential sentence
* Update docs/pages/admin-guides/management/guides/aws-iam-identity-center/migrating-identity-center-from-okta-to-teleport.mdx
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Add cdocumentation for `workload-identity-aws-ra` service
* Apply suggestions from code review
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Adjust name to be full roles anywhere
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Edit DNS guidance for registered apps
Closes#30361
Add an explicit warning against creating DNS records that map
application subdomains to the hosts of registered applications. Use the
`dns-app-access` partial in `connecting-apps.mdx` to simplify reuse.
* Respond to zmb3 feedback
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
---------
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
See gravitational/docs-website#97
The docs engine removes these using a custom plugin during builds.
Remove string styles in the docs content so we can remove the plugin.
* Update protobuf
* Implement and test ValidateTokenWithJWKS
* Update join logic to use new method for static jwks
* Update Terraform Provider
* Update operator docs/files
* Update goldenfile
Include inlining the partial:
docs/pages/includes/machine-id/recover-circle-ci-claims.mdx
This is because it's only used by two pages and, as a partial, violates
the rule in which each Var with a given name must be used multiple
times on a single page. Since this Vale rule uses the `raw` scope, it is
not possible to ignore it with an MDX comment.
DocCardList is a Docusaurus-native component that achieves the same
goal as our custom `remark-toc` plugin, but with Docusaurus APIs instead
of file system lookups. Replace `(!toc!)` mentions so we can remove
`remark-toc`.
Closes#52000
Add an H3 section to the Linux H2 of the Installation guide clarifying
that users must create a configuration file and linking to guidance on
doing so.
The guide now reflects that rolling Auth upgrades are allowable in
certain scenarios. The guide also explicitly calls out when client
tools should be upgraded.
Closes#5377
Aside from a Route 53 zone and key pair, the two Terraform modules for
self-hosted clusters do not require existing resources. Clarify the
additional prerequisites in the Prerequisites sections of these guides.
Add bullets to existing prerequisites to make these sections consistent
with other docs guides.
* minimal draft
* Add note on enabling TLS for Oracle RDS
* Full Oracle RDS guide
* update SQL Server adutil installation instructions
* Update Oracle RDS database documentation to include audit logging steps. Small corrections to self-hosted guide.
* Fix typos
* Apply suggestions from code review
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Remove tabs
* Address part of review comments
* add small comments
* Apply suggestions from code review
Co-authored-by: Gabriel Corado <gabriel.oliveira@goteleport.com>
* expand troubleshooting, tls setup
* note on SQLcl and alternatives
* misaligned columns aligned shall be now
* Typos/spelling
* drop empty line
* Optimize PNG
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Gabriel Corado <gabriel.oliveira@goteleport.com>
This adds a new field, UseAnyProxyPublicAddr, that will be used to
tell the web api/ui to rebuild the request app's FQDN based on the proxy
public addr that the request came from (upcoming PR to consume this)
This commit adds two new singular resources to the Terraform provider:
teleport_version and telpeort-config.
Both got added using the resource 153 pattern (new protoc-X.yaml file)
and it went pretty seamless.
The only specific is that I had to add a provider feature to
automatically set singular resource names as we don't run
CheckAndSetDefaults() locally anymore. This got merged in a separate PR.
* Reorganize the feature matrix
This change organizes the feature matrix according to the latest product
categorization scheme, and moves the feature matrix into its own guide
to make it more discoverable. While there is opportunity to rework the
rows within the feature matrix, this change minimizes the scope of the
first iteration by reorganizing the existing rows while leaving them for
the most part unchanged.
In the new feature matrix page, each Teleport product has its own
H2-level section. Product descriptions come from official Marketing
language, focusing on concrete statements about what each product
comprises and how it works and leaving out statements of value (which
are not typically found in documentation). This change does not include
sections for categories with no rows in the current table.
* Respond to zmb3 feedback
Add minor wording tweaks.
* Align cells across feature matrix tables
Make it easier for a user to follow a single column across multiple
tables of the feature matrix. Since the style sets cells to 25% width,
which assumes a table that is four cells wide, use a `style` tag so the
style only applies to the tables in the `teleport-editions.mdx` guide.
Closesgravitational/docs-website#134
* Update the MWI section of the feature matrix
Indicate that it is available for Community Edition users.
* Edit index.mdx
Apply changes made to identical language in teleport-editions.mdx.
* Respond to eglenn-teleport feedback
- Move the Community Edition column to the final place, rather than the
first, since we now want to de-emphasize Community Edition and elevate
the commercial offering.
- Edit the text to de-emphemphasize "editions", moving the description
of editions to the end of the page and linking to this from the
heading of relevant feature matrix columns.
- Remove section intro paragraphs, since the same information is
on the home page of the docs.
* Add a Teleport Identity Security section
Co-authored-by: Ben Arent <ben@goteleport.com>
* Rename MWI features
---------
Co-authored-by: Ben Arent <ben@goteleport.com>
When converting one `Details` component into semantic HTML tags,
`Details` attributes were left by mistake a `summary` tag. This change
fixes the issue.
Ports #53003 to `master`
This change helps guarantee that we'll update the version support table
at the same time as the upcoming release table to keep our support
windows up to date. Since we otherwise do not update the two tables at
the same time, the supported version table has become out of date.
This change also updates support windows based on the plan to release
v18 in May, 2025, with the assumption that we release a major version
every 4 months.
This change also moves the compatibility description from FAQ to
Upcoming Releases so we keep this info in one place, and links to
Upcoming Releases from the relevant section of the FAQ.
Since the docs engine automatically copies the Upcoming Releases page
from the default version to all four versions of the docs, this change
does not edit the Upcoming Releases page for this version.
This change removes an item from the docs test plan re: editing the
supported versions table, since we'll be doing this continuously rather
than when we release a new major version.
See gravitational/docs-website#91
Docusaurus uses semantic HTML tags instead of a custom Details
component. Replace instances of our Details component with the
`<details>` and `<summary>` tags so we do not need to perform a
conversion when building the docs website.
Closesgravitational/docs-website#70
`Tabs` components that use a dropdown menu do not render on the
Docusaurus site. Since there are not many of these in the docs content,
it makes sense to change them to standard `Tabs` components instead of
porting the legacy `Tabs` behavior to the new Docusaurus site.
- Change long picker partials to use a standard `Tabs` component instead
of a dropdown menu. While this is not ideal, it standardizes the
`Tabs` component in the docs to only use attributes that the docs
engine can process. All `TabItems` render as expected.
- Remove an unused partial that uses two-dimensional `Tabs`
(`docs/pages/includes/install-linux-self-hosted.mdx`).
- In some guides, collapse two-dimensional `Tabs` components to only
require one dimension.
- In `install-linux-enterprise.mdx`, use the one-line installation
script to simplify the instructions and avoid using `Tabs` entirely.
Dan Upton