-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Document additional credential providers for JDBC connectors #14454
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
53 changes: 53 additions & 0 deletions
53
docs/src/main/sphinx/connector/jdbc-authentication.fragment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| Data source authentication | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| The connector can provide credentials for the data source connection | ||
| in multiple ways: | ||
|
|
||
| * inline, in the connector configuration file | ||
| * in a separate properties file | ||
| * in a key store file | ||
| * as extra credentials set when connecting to Trino | ||
nineinchnick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| You can use :doc:`secrets </security/secrets>` to avoid storing sensitive | ||
| values in the catalog properties files. | ||
|
|
||
| The following table describes configuration properties | ||
| for connection credentials: | ||
|
|
||
| .. list-table:: | ||
| :widths: 40, 60 | ||
| :header-rows: 1 | ||
|
|
||
| * - Property name | ||
| - Description | ||
| * - ``credential-provider.type`` | ||
| - Type of the credential provider. Must be one of ``INLINE``, ``FILE``, or | ||
| ``KEYSTORE``; defaults to ``INLINE``. | ||
| * - ``connection-user`` | ||
| - Connection user name. | ||
| * - ``connection-password`` | ||
| - Connection password. | ||
| * - ``user-credential-name`` | ||
| - Name of the extra credentials property, whose value to use as the user | ||
| name. See ``extraCredentials`` in :ref:`jdbc-parameter-reference`. | ||
| * - ``password-credential-name`` | ||
| - Name of the extra credentials property, whose value to use as the | ||
| password. | ||
| * - ``connection-credential-file`` | ||
| - Location of the properties file where credentials are present. It must | ||
| contain the ``connection-user`` and ``connection-password`` properties. | ||
| * - ``keystore-file-path`` | ||
| - The location of the Java Keystore file, from which to read credentials. | ||
| * - ``keystore-type`` | ||
| - File format of the keystore file, for example ``JKS`` or ``PEM``. | ||
| * - ``keystore-password`` | ||
| - Password for the key store. | ||
| * - ``keystore-user-credential-name`` | ||
| - Name of the key store entity to use as the user name. | ||
| * - ``keystore-user-credential-password`` | ||
| - Password for the user name key store entity. | ||
| * - ``keystore-password-credential-name`` | ||
| - Name of the key store entity to use as the password. | ||
| * - ``keystore-password-credential-password`` | ||
| - Password for the password key store entity. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.