Created on 12-15-2025 09:56 AM - edited 12-15-2025 10:12 AM
Hello community, greetings again. I'm currently analyzing how to migrate from NIFI 1.11.4 to 2.0. My strategy is to create and export my workflow template to version 1.9.2, which worked correctly. Now, from there, I want to migrate to version 2.0. Using the same method, all of this done locally on Windows, to later install the final version of the NiFi cluster from a Docker image, the problem I encountered is that version 2.0 of NiFi requires a username and password. Upon reviewing comments and documentation on the matter, I see that they indicate extracting the user from the nifi-app.log file, searching for "0" in the "Generated Username" file, but that doesn't appear in my log file, and I also can't find the Windows command to generate the user; I only see it for Linux. My question is, is there any method to generate users in Windows, or is there any... HOW TO DEFINE IT IN THE login-identity-providers.xml FILE?
Created 12-15-2025 12:51 PM
Created 12-15-2025 12:51 PM
Created 12-15-2025 01:37 PM
@Bern
The single-user-provider authentication login provider and Single-User-Authorizer are extremely basic and only intended for out-of-the-box Apache NiFi product evaluation. Apache NiFi also generates simple self-signed certificates to support the secured connection over HTTPS. For more robust security you should be using a different multi-user authentication provider like ldap-provider and a multi-user authorizer like the managed-authorizer. You should also generate signed certificates. The Self-signed certificates generated by NiFi will eventually expire.
Reference:
User Authentication
Multi-Tenant Authorization
Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.
Thank you,
Matt