Hi Balaji:
I agree storing audit data in DB is not scalable for long term data.
What would be the path forward for users who are already using DB to store
audit data and managing the DB themselves?
Adding user@ranger list.
Thank you,
Vel
On 3/8/16, 3:19 PM, "Balaji Ganesan"
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
Hello !
I send you this mail concerning the property "xml_configurations_supported".
I cannot find any information about this property in the documentation.
What is the définition of the property "xml_configurations_supported" ?
Best regards.
Lune
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.
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