Shouldn't allow proceeding with setup after errors during the launch

Description

If a Windows user install Openfire into Program files folder and runs the launcher without Run as admin option (even if he is logged in as administrator), the launcher shows errors, but the user is still allowed to proceed with setup and eventually stumbles on the "current password" error, which is not present when the launcher is running as it should with Run as admin option or Openfire is not installed into Program files or Openfire is running as a service (with SYSTEM permission in that case). Openfire shouldn't allow continuing with setup in such case. Error:

Environment

Windows with UAC protection; Debian when running with a regular user

Activity

Show:
wroot
February 22, 2019, 8:08 PM

So, my issue with Debian was not an issue. I just didn't know it already creates openfire user and runs with it. But the main issue is still here, Openfire is showing Current password prompt, when setup is running without needed permissions, which is confusing and shouldn't be shown.

wroot
February 22, 2019, 4:03 PM

Actually, deb package creates a user openfire:openfire and daemon runs with it, so there is no need to change permissions, all folders already are owned by openfire user.

wroot
February 14, 2019, 3:07 PM

I have installed Openfire via dpkg, but i had to use sudo to install. To run it with a regular user i had to change permissions to my user instead of su. But i think i miss something still and i get Current password prompt on a fresh install.

sudo chown -R test:users /usr/share/openfire
sudo chown -R test:users /etc/openfire (conf)
sudo chown -R test:users /var/log/openfire (logs)
sudo chown test:users /var/run/openfire.pid (pid)

then i run with user test: /etc/init.d/openfire start

it complains about not being able to set gid, but setup is running

wroot
February 14, 2019, 7:16 AM

Assignee

Unassigned

Reporter

wroot

Expected Effort

None

Ignite Forum URL

None

Components

Affects versions

Priority

Major