svn commit: r1893880 - /nifi/site/trunk/quickstart.html

[jg...@apache.org]

Author: jgresock
Date: Mon Oct  4 13:52:57 2021
New Revision: 1893880

URL: http://svn.apache.org/viewvc?rev=1893880&view=rev
Log:
Update startup url on quickstart.md

Modified:
    nifi/site/trunk/quickstart.html

Modified: nifi/site/trunk/quickstart.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/quickstart.html?rev=1893880&r1=1893879&r2=1893880&view=diff
==============================================================================
--- nifi/site/trunk/quickstart.html (original)
+++ nifi/site/trunk/quickstart.html Mon Oct  4 13:52:57 2021
@@ -197,11 +197,6 @@ Include <code>-DskipTests</code> to comp
 <p>Now you should have a fully functioning build off the latest codebase.</p>
 <p><strong>NOTE:</strong>  During development it is not necessary to build the entire code base. Typically, in case of a NAR bundle change you can build only the particular bundle followed by running <code>mvn -T C2.0 clean install -Ddir-only</code> in <code>nifi-assembly</code>.</p>
 <h2>Running the application</h2>
-<h4>** WARNING **</h4>
-<p>Without any configuration, the application will run on port <code>8080</code> and does not require any credentials to modify<br>
-the flow. This means of running Apache NiFi should be used only for development/testing and in an environment where only<br>
-connections from trusted computers and users can connect to port <code>8080</code>. Using iptables to allow only localhost connections<br>
-to <code>8080</code> is a good start, but on systems with multiple (potentially untrusted) users, also not a sufficient protection.</p>
 <h4>Decompress and launch</h4>
 <p>Running the above build will create a <em>tar.gz</em> (and <em>zip</em>) file in <code>./nifi-assembly/target</code>. This <em>tar.gz</em> should<br>
 contain the full application. Decompressing the <em>tar.gz</em> should make a directory for you containing several other<br>
@@ -226,7 +221,11 @@ to run as, which Java command to use, et
 <p>The entire concept of how the application will integrate to a given OS and run as an<br>
 enduring service is something we're working hard on and would appreciate ideas for.  The user experience needs to<br>
 be excellent.</p>
-<p>With the default settings you can point a web browser at <code>http://localhost:8080/nifi/</code></p>
+<p>With the default settings you can point a web browser at <code>https://127.0.0.1:8443/nifi</code></p>
+<p>The default installation generates a random username and password, writing the generated values to the application log. The application log is located in <code>logs/nifi-app.log</code> under the installation directory. The log file will contain lines with <code>Generated Username [USERNAME]</code> and <code>Generated Password [PASSWORD]</code> indicating the credentials needed for access. Search the application log for those lines and record the generated values in a secure location.</p>
+<p>The following command can be used to change the username and password:</p>
+<pre><code>$ ./bin/nifi.sh set-single-user-credentials &lt;username&gt; &lt;password&gt;
+</code></pre>
 <p>Logging is configured by default to log to <em>./logs/nifi-app.log</em>. The following log message should indicate the web UI<br>
 is ready for use:</p>
 <pre><code>2014-12-09 00:42:03,540 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs: