scottyaslan commented on code in PR #10370:
URL: https://github.com/apache/nifi/pull/10370#discussion_r2403595590


##########
nifi-frontend/src/main/frontend/apps/nifi-registry/README.md:
##########
@@ -0,0 +1,335 @@
+<!--
+  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.
+-->
+
+# NiFi Registry LDAP setup
+
+This document contains instructions for testing the NiFi Registry LDAP 
Identity Provider and LDAP User Group Provider.
+
+It utilizes a publicly accessible LDAP test server, made available by Forum 
Systems. For more information on this server, see:
+
+http://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/
+
+## Configuring NiFi Registry for HTTPS
+
+nifi-registry.properties is located in 
nifi-registry/nifi-registry-assembly/target/nifi-registry-2.7.0-SNAPSHOT-bin/nifi-registry-2.7.0-SNAPSHOT/conf/.
 You will need to update that file to configure the nifi registry to run 
securely with LDAP.
+
+For running a NiFi Registry on localhost, you should already have test keys 
and certs in your locally built clone of the nifi registry source code 
repository:
+
+    /path/to/nifi-registry/nifi-registry-web-api/src/test/resources/keys/

Review Comment:
   This has been updated. Thanks for testing it out!



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to