Thank for the quick turn-around on this, Bryan. Responses are in-line, below.
Bryan Bende wrote > Can you explain a little more about what you mean by "scripts containing > compile errors"? Are you talking about ExecuteScript processors? Yes, they are errors in the Groovy code inserted into ExecuteScript Processor. Mostly, the error lies in the change from "ProcessLog" to "ComponentLog". My question is can the security migration work and can I use the NiFi GUI when such errors exist in the flow.xml.gz file? Bryan Bende wrote > I would expect the following to work... > > - Take a brand new Apache NiFi 1.0.0 tar/zip and extract it > - Copy flow.xml.gz from old NiFi to NiFi 1.0.0/conf/ > - Configure nifi.properties for NiFi 1.0.0 to setup the https host/port > and > all the SSL properties, and specify the file-authorizer > (nifi.security.user.authorizer=file-provider) > - Configure the file-authorizer in NiFi 1.0.0/conf/authorizers.xml and set > the path to old authorized-users.xml > - Then start NiFi 1.0.0 This is how I finally got it working, but I did it without using the old flow file, due to the errors I was getting. This apparently resulted in my not being able to edit my flows once I stopped, added my old flows, started, and logged in. Bryan Bende wrote > If you are trying to reconfigure the NiFi 1.0.0 that you already setup, > you > will want to delete the users.xml and authorizations.xml from the conf > directory if you want it to regenerate the conversion from the legacy > authorized-users.xml. > It only attempts the legacy conversion the first time when no users, > groups, and policies exist. Yes, I have done this once before based on your documentation on the Wiki. However, with a blank flow file. Bryan Bende wrote > The app log you linked to shows that your nifi.properties did not have an > authorizer set, basically nifi.security.user.authorize was empty in > nifi.properties, and therefore NiFi could not start in secure mode. I apologize, I was in the process of reverting to version 0.8.0, so may have sent you the wrong properties file. I have also tried to disable security in 1.0.0, but I still cannot get it working. I will try one more time to start from the initial start-up and build the users.xml and authorizations.xml from the old authorized-users.xml as you described, but this time with my 0.8.0 flows in place (errors and all). If that does not work, I will create another flow in another instance that does not have any ScriptExecutor processors in it, then use that as a starting point. Does that sound like a good plan? -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Questions-regarding-security-set-up-in-NiFi-1-0-0-tp13288p13300.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
