[jira] [Closed] (UNOMI-478) Docker image could not be configured to connect to Elastic Search when authorization is needed

["Serge Huber (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/UNOMI-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Huber closed UNOMI-478.
-----------------------------
    Resolution: Fixed

The env variables already exist, they are just not properly used in the Docker image's entrypoint.sh script:

From custom.system.properties:
{code}
org.apache.unomi.elasticsearch.username=${env:UNOMI_ELASTICSEARCH_USERNAME:-}
org.apache.unomi.elasticsearch.password=${env:UNOMI_ELASTICSEARCH_PASSWORD:-}
{code}

Closing this issue since UNOMI-479 already exists to modify the entrypoint.sh script.

> Docker image could not be configured to connect to Elastic Search when authorization is needed
> ----------------------------------------------------------------------------------------------
>
>                 Key: UNOMI-478
>                 URL: https://issues.apache.org/jira/browse/UNOMI-478
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0, 1.5.5
>            Reporter: Risto
>            Priority: Major
>
> I found that using the delivered docker container it is impossible to connect to elastic that needs authentication. Documentation says:
>   
>  3.14.1. User authentication !
>  If your ElasticSearch have been configured to be only accessible by authenticated users. Just edit etc/org.apache.unomi.persistence.elasticsearch.cfg to add the following settings:
>  username=USER
>  password=PASSWORD
>   
>  But this can not be done by setting environment variables outside docker container.  New environment variables like ELASTIC_USERNAME, ELASTIC_PASSWORD are needed. It should default to no password and no username as it does now. 
>   
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)