Hey Gautam, an additionnal question here.

For usersync, I have the impression that I have the same kind of situation :
- ranger.usersync.credstore.filename
- ranger.usersync.keystore.file

Is that the same ?

I mean, the credstore contains all the passwords using the Hadoop
Credential Provider and the keystore file is to activate ssl for usersync ?

Best regards.

Tale.

On Tue, Mar 22, 2016 at 11:28 AM, Lune Silver <lunescar.ran...@gmail.com>
wrote:

> Hello Gautam.
>
> Thank you for your answer.
>
> Best regards.
>
> Lune.
>
>
>
>
>
> On Tue, Mar 22, 2016 at 11:13 AM, Gautam Borad <gbo...@gmail.com> wrote:
>
>> Hi Lune,
>>     These are two different properties that we are talking about here.
>>
>>    - *ranger.https.attrib.keystore.**file* : This property is for
>>    providing the location of the server keystore certificate to be loaded (
>>    Public CA issued keystore ). You can find more info here.
>>    <https://tomcat.apache.org/tomcat-7.0-doc/config/http.htm>
>>
>>
>>    - *ranger.credential.provider.**path* : This property is for
>>    providing the location of local credential file, which will store DB 
>> /Audit
>>    DB  / LDAP Bind DN etc passwords using the Hadoop CredentialProvider.
>>
>>
>> For SSL you should look more into the ranger.https.attrib.keystore.file
>> property.
>>
>>
>> On Tue, Mar 22, 2016 at 3:18 PM, Lune Silver <lunescar.ran...@gmail.com>
>> wrote:
>>
>>> Hello !
>>>
>>> I'm currently writing an installation book for my team and myself and
>>> I'm in the Advanced ranger-admin-site in Ambari UI.
>>>
>>> In this part, I can see two parameters :
>>> - ranger.credential.provider.path : file for credential store
>>> - ranger.https.attrib.keystore.file : ranger admin keystore
>>>
>>> Q1 - What is the difference between these two properties ? What exactly
>>> does each of this property do ?
>>>
>>> Q2 - If I want to enable the secured connection to the Ranger Admin UI,
>>> which one interests me ?
>>>
>>> Best regards.
>>>
>>> Lune.
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Gautam.
>>
>
>

Reply via email to