[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136031#comment-15136031
]
Andre edited comment on NIFI-1461 at 2/6/16 10:34 PM:
------------------------------------------------------
[~jameswing]
At the present when I install from RPM I need to:
- add a user so I can use {{run.as=nifi}} or to use it with {{nifi.sh start}}
as that user.
- I need to modify the permissions so that {{/opt/nifi/nifi-*/}} is at least
readable by nifi group, although the sections of the folder structure holding
writeable data (e.g. {{./conf/flow.xml.gz}} ) must be writeable by {{nifi}} as
well.
The point is: There is very few reasons why NiFi would need to run as root (I
can't find one to be honest), so ideally the RPM should result on a state where
a user could simply {{runas}} or {{sudo}} and be able to login to a functional
nifi web interface.
was (Author: trixpan):
[~jameswing]
At the present when I install from RPM I need to:
- add a user so I can use {{run.as=nifi}} or to use it with {{nifi.sh start}}.
- I need to modify the permissions so that {{/opt/nifi/nifi-*/}} is at least
readable by nifi group, although the sections of the folder structure holding
writeable data (e.g. {{./conf/flow.xml.gz}} ) must be writeable by {{nifi}} as
well.
The point is: There is very few reasons why NiFi would need to run as root (I
can't find one to be honest), so ideally the RPM should result on a state where
a user could simply {{runas}} or {{sudo}} and be able to login to a functional
nifi web interface.
> 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
> Attachments: 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)
