[
https://issues.apache.org/jira/browse/KNOX-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2851:
--------------------------------
Description:
Currently, there are two ways to set up a connection from Knox to a PostgreSQL
instance:
* either using the connection JDBC URL
* or specifying the connection parameters (host, port, etc...) one by one
In the case of the first option, the username and password information has to
be part of the URL in plain text which should be avoided. Therefore these two
sensitive parameters should be configured just like we do in the 2nd case.
Moreover, SSL configuration (added in KNOX-2598) is only available for the
second case. This has to be addressed as well.
was:
Currently, there are two ways to set up a connection from Knox to a PostgreSQL
instance:
* either using the connection JDBC URL
* or specifying the connection parameters (host, port, etc...) one by one
In the case of the first option, the username and password information has to
be part of the URL in plain text which should be avoided. Therefore these two
sensitive parameters should be configured just like we de in the 2nd case.
> Support additional username/password settings in PostgeSQL
> ----------------------------------------------------------
>
> Key: KNOX-2851
> URL: https://issues.apache.org/jira/browse/KNOX-2851
> Project: Apache Knox
> Issue Type: Task
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently, there are two ways to set up a connection from Knox to a
> PostgreSQL instance:
> * either using the connection JDBC URL
> * or specifying the connection parameters (host, port, etc...) one by one
> In the case of the first option, the username and password information has to
> be part of the URL in plain text which should be avoided. Therefore these two
> sensitive parameters should be configured just like we do in the 2nd case.
> Moreover, SSL configuration (added in KNOX-2598) is only available for the
> second case. This has to be addressed as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
