Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.5.0
-
None
Description
To enable security we need add following properties to falcon-startup.properties:
"*.falcon.http.authentication.kerberos.principal":"HTTP/_HOST@EXAMPLE.COM" "*.falcon.http.authentication.kerberos.keytab":"/etc/security/keytabs/spnego.service.keytab" "*.falcon.service.authentication.kerberos.principal":"falcon/_HOST@EXAMPLE.COM" "*.falcon.service.authentication.kerberos.keytab":"/etc/security/keytabs/falcon.service.keytab" "*.dfs.namenode.kerberos.principal":"nn/_HOST@EXAMPLE.COM" "*.falcon.http.authentication.type":"kerberos" "*.falcon.authentication.type":"kerberos"
Also, we need to add
<properties> <property name="dfs.namenode.kerberos.principal" value="nn/_HOST@EXAMPLE.COM" /> </properties>
in cluster definition to make it works in secured mode.
Attachments
Attachments
Issue Links
- is related to
-
AMBARI-5012 Security Wizard: Verify Falcon service works with Kerberos envirnonment.
- Resolved