[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141458#comment-15141458
]
James Wing commented on NIFI-1461:
----------------------------------
I applied the two attached patches to master and built an RPM with {{mvn clean
install -Prpm}}. The RPM installs correctly, and now runs as 'nifi' by
default. Good stuff!
But it seems that the .zip, .tar.gz, and directory assemblies also have the
{{run.as=nifi}} setting applied to bootstrap.conf when -Prpm is specified in
the build. Running the build again as {{mvn clean install}} (no -Prpm),
results in assemblies without the {{run.as=nifi}}. Since the RPM build is an
optional extra, this might not be a problem, but it did not strike me as
obvious. Is this expected and OK?
> RPM should create nifi user and give it access to the /opt/nifi and
> subdirectories
> ----------------------------------------------------------------------------------
>
> Key: NIFI-1461
> URL: https://issues.apache.org/jira/browse/NIFI-1461
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.4.1
> Reporter: Andre
> Assignee: Tony Kurc
> Labels: rpm
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1461-This-closes-204.-Implemented-RPM-before-af.patch,
> 0002-NIFI-1461-added-run.as-filtered-property-for-RPM-and.patch, nifi.spec,
> nifi.spec
>
>
> currently when installing from RPM the resulting permissions result on admins
> having to complete the installation by adding a user and correcting
> filesystem permissions.
> Ideally the RPM packages should result in installed files ready to be
> utilised as a non-root user
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
