[
https://issues.apache.org/jira/browse/KNOX-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644193#comment-17644193
]
ASF subversion and git services commented on KNOX-2851:
-------------------------------------------------------
Commit 618e7e10db2076c4de4aca19112c2f6deb8bfc09 in knox's branch
refs/heads/dependabot/npm_and_yarn/knox-token-management-ui/decode-uri-component-0.2.2
from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=618e7e10d ]
KNOX-2851 - Username and password properties can be set as aliases even when
clients use JDBC URL. (#699)
SSL configuration happens for both connection types (JDBC URL or separate
property declaration).
> 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
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
