​As the Knox user, create a nifi-ca-config.json file on each Knox node, in a location accessible to Knox.

For example, to create the file on a Knox node at /home/knox using the vi text editor, enter the following:

sudo su - knox
vi /home/knox/nifi-ca-config.json 

​Populate the nifi-ca-config.json file with the following information:

{
  "dn" : "CN=$KNOX_HOSTNAME, OU=KNOX",
  "keyStore" : "/home/knox/knox-nifi-keystore.jks",
  "keyStoreType" : "jks",
  "keyStorePassword" : "$KEYSTORE_PASSWORD",
  "keyPassword" : "$KEY_PASSWORD",
  "token" : "$NIFI_CA_TOKEN_VALUE",
  "caHostname" : "$NIFI_CA_HOSTNAME",
  "port" : $NIFI_CA_PORT,
  "trustStore" : "/home/knox/knox-nifi-truststore.jks",
  "trustStorePassword" : "$TRUSTSTORE_PASSWORD",
  "trustStoreType" : "jks"
}

	Note
	You can set keyStorePassword, keyPassword, and trustStorePassword to the Knox Master Secret to make it easier to import the keyStore and trustStore created by the NiFi Certificate Authority into the Knox keystore.

As the root user, start the NiFi TLS Toolkit:For the location of the TLS Toolkit, see the HDF Release Notes for release-specific download information.

/var/lib/ambari-agent/tmp/nifi-toolkit-1.5.0.3.1.0.0-564/bin/tls-toolkit.sh
client --subjectAlternativeNames "CN=$KNOX_HOSTNAME, OU=KNOX"
-F
-f /home/knox/config.json

The toolkit requests a new certificate and creates two new files containing the keystore and truststore:

/home/knox/knox-nifi-keystore.jks
/home/knox/knox-nifi-truststore.jks

Import the Knox certificate for NiFi into the Knox gateway.jks file:

keytool
-importkeystore
-srckeystore /home/knox/knox-nifi-keystore.jks
-destkeystore /usr/hdp/current/knox-server/data/security/keystores/gateway.jks
-deststoretype JKS
-srcstorepass $KEYSTORE_PASSWORD
-deststorepass $KNOX_MASTER_PASSWORD

The gateway.jks file should now contain a PrivateKeyEntry for NiFi.

Import the NiFi CA truststore into the Knox gateway.jks file:

keytool
-importkeystore
-srckeystore /home/knox/knox-nifi-truststore.jks
-destkeystore /usr/hdp/current/knox-server/data/security/keystores/gateway.jks
-deststoretype JKS
-srcstorepass $KEYSTORE_PASSWORD
-deststorepass $KNOX_MASTER_PASSWORD

The gateway.jks file should now contain a trustedCertEntry for NiFi.

Knox uses the gateway.jks file to fince secure certificates in the truststore.

Verify that the proper keys are in the gateway.jks file:

keytool
-keystore /usr/hdp/current/knox-server/data/security/keystores/gateway.jks
-storepass $KEYSTORE_PASSWORD
-list
-v

You should see nifi-key and nifi-cert added to the gateway-identity key.

As the Knox user, create flow-management.xml in /usr/hdp/current/knox-server/conf/topologies.

Add the following content to flow-management.xml:

If you have modified the ShiroProvider in the topology specified in the Advanced Topology section of the Ambari Knox configs, and want to authenticate Flow Management topology users in the same manner as Advanced Topology users, ensure that those modifications are reflected in your added content.

<?xml version="1.0" encoding="utf-8"?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->
<topology>
  <gateway>
    <provider>
      <role>authentication</role>
      <name>ShiroProvider</name>
      <enabled>true</enabled>
      <param>
        <name>sessionTimeout</name>
        <value>30</value>
      </param>
      <param>
        <name>redirectToUrl</name>
        <value>/gateway/knoxsso/knoxauth/login.html</value>
      </param>
      <param>
        <name>restrictedCookies</name>
        <value>rememberme,WWW-Authenticate</value>
      </param>
      <param>
        <name>main.ldapRealm</name>
        <value>org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm</value>
      </param>
      <param>
        <name>main.ldapContextFactory</name>
        <value>org.apache.hadoop.gateway.shirorealm.KnoxLdapContextFactory</value>
      </param>
      <param>
        <name>main.ldapRealm.contextFactory</name>
        <value>$ldapContextFactory</value>
      </param>
      <param>
        <name>main.ldapRealm.userDnTemplate</name>
        <value>uid={0},ou=people,dc=hadoop,dc=apache,dc=org</value>
      </param>
      <param>
        <name>main.ldapRealm.contextFactory.url</name>
        <value>ldap://localhost:33389</value>
      </param>
      <param>
        <name>main.ldapRealm.authenticationCachingEnabled</name>
        <value>false</value>
      </param>
      <param>
        <name>main.ldapRealm.contextFactory.authenticationMechanism</name>
        <value>simple</value>
      </param>
      <param>
        <name>urls./**</name>
        <value>authcBasic</value>
      </param>
    </provider>
    <provider>
      <role>identity-assertion</role>
      <name>Default</name>
      <enabled>true</enabled>
    </provider>
  </gateway>
  <service>
    <role>NIFI</role>
    <url>$NIFI_HTTP_SCHEME://$NIFI_HOST:$NIFI_HTTP_SCHEME_PORT</url>
    <param name="useTwoWaySsl" value="true"/>
  </service>
</topology>

Save the configuration and restart Knox, or continue by configuring Knox SSO.

Navigate to Advaned knoxsso-topology and, in the KNOXSSO service definition, edit

If you want to use Knox SSO authentication, perform the following steps:

Save the configuration and restart Knox.