lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Jackson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4392) DIH - Need to externalize or encrypt username/password stored within data-config.xml
Date Thu, 06 Oct 2016 16:20:21 GMT

    [ https://issues.apache.org/jira/browse/SOLR-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552385#comment-15552385
] 

Jamie Jackson commented on SOLR-4392:
-------------------------------------

As far as I know, the only place where encrypted passwords are documented is in https://cwiki.apache.org/confluence/display/solr/Uploading+Structured+Data+Store+Data+with+the+Data+Import+Handler,
under the "Configuring the DIH Configuration File", in a comment of a sample XML file:

{code:xml}
<!--
Alternately the password can be encrypted as follows. This is the value obtained as a result
of the command
openssl enc -aes-128-cbc -a -salt -in pwd.txt
password="U2FsdGVkX18QMjY0yfCqlfBMvAB4d3XkwY96L7gfO2o=" 
WHen the password is encrypted, you must provide an extra attribute
encryptKeyFile="/location/of/encryptionkey"
This file should a text file with a single line containing the encrypt/decrypt password
-->
{code}

Unfortunately, [I can't get it to work|http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201610.mbox/%3CCA%2BonWPfGakOUO0VJqBYfnALfq61HfysL0Uv%2BG8p-TRL0P44NOQ%40mail.gmail.com%3E].

> DIH - Need to externalize or encrypt username/password stored within data-config.xml
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-4392
>                 URL: https://issues.apache.org/jira/browse/SOLR-4392
>             Project: Solr
>          Issue Type: New Feature
>          Components: contrib - DataImportHandler
>    Affects Versions: 4.0, 4.1
>            Reporter: Senthuran Sivananthan
>            Assignee: Noble Paul
>             Fix For: 5.2, 6.0
>
>         Attachments: SOLR-4392.patch, SOLR-4392.patch
>
>
> Today, the connection (database or otherwise) credentials is wide open in data-config.xml.
 Not really an issue until someone sends out the config file outside of the server.
> We should look into externalizing the database lookup or providing a way to encrypt the
username and password.
> The needs are:
> 1/  Some projects want to enable multi-tenancy where data for each core is situated in
different database servers w/ their own credentials.  We need a way to expose hooks that will
allow implementations to be plugged in.  It can be done though the "type" attribute on the
dataSource, but providing a factory might work better.
> 2/  Most orgs are very protective of their credentials and weary of plain-text settings.
> {code:xml}
> <dataSource name="jdbc" driver="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@//hostname:port/SID"
user="db_username" 
> <!-- This database password is encrypted using AES using the command. pwd.txt contains
the actual DB password -->
> <!-- openssl enc -aes-128-cbc -a -salt -in pwd.txt -->
> password="U2FsdGVkX18QMjY0yfCqlfBMvAB4d3XkwY96L7gfO2o=" 
> <!-- Password to decrypt is stored in this file-->
> encryptKeyFile="/location/of/encryptionkey"
> />
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message