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.

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

DB GUI Docs: Specify certs to the proper fields in DB GUI configuration instructions #20344

Closed
gaille-teleport opened this issue Jan 18, 2023 · 0 comments · Fixed by #46318
Closed
Assignees
Labels
database-access Database access related issues and PRs documentation

Comments

@gaille-teleport
Copy link

Applies To

https://goteleport.com/docs/connect-your-client/gui-clients/?scope=enterprise

Details

Instructions to add the various generated cert files to the configuration fields in DB GUIs should be clearer. Users might not know which cert file to add to each of these fields. For example for pgAdmin:

cert_file -> Client Certificate
key_file -> Client Certificate Key
ca_file -> Root Certificate

pgadmin-ssl@2x

Applies also for these DB GUI instructions:

@stevenGravy stevenGravy added the database-access Database access related issues and PRs label Jan 19, 2023
@ptgott ptgott self-assigned this Sep 5, 2024
ptgott added a commit that referenced this issue Sep 5, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
ptgott added a commit that referenced this issue Sep 11, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
ptgott added a commit that referenced this issue Sep 11, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
github-merge-queue bot pushed a commit that referenced this issue Sep 11, 2024
* Clarify TLS paths in the database GUI guide

Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.

* Respond to ravicious feedback

- Change table order
- Clarify note re: copying files
github-actions bot pushed a commit that referenced this issue Sep 11, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
github-actions bot pushed a commit that referenced this issue Sep 11, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
github-actions bot pushed a commit that referenced this issue Sep 11, 2024
Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.
github-merge-queue bot pushed a commit that referenced this issue Sep 11, 2024
* Clarify TLS paths in the database GUI guide

Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.

* Respond to ravicious feedback

- Change table order
- Clarify note re: copying files
github-merge-queue bot pushed a commit that referenced this issue Sep 12, 2024
* Clarify TLS paths in the database GUI guide

Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.

* Respond to ravicious feedback

- Change table order
- Clarify note re: copying files
github-merge-queue bot pushed a commit that referenced this issue Sep 12, 2024
* Clarify TLS paths in the database GUI guide

Closes #20344

Make more explicit correspondences between TLS credential paths returned
by `tsh proxy db` and configuration fields in four GUI clients.

* Respond to ravicious feedback

- Change table order
- Clarify note re: copying files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database-access Database access related issues and PRs documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants