Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Web Administrator user account from 3.3 not enabled in 3.4

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Web Administrator user account from 3.3 not enabled in 3.4


Chronological Thread 
  • From: Peter Gutierrez <>
  • To:
  • Subject: [perfsonar-user] Web Administrator user account from 3.3 not enabled in 3.4
  • Date: Wed, 08 Oct 2014 15:24:28 -0400
  • Organization: Gang of Peters

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In another thread on 10/08/2014 02:57 PM, Andrew Lake wrote:
> - It is intentional that you cannot login as root to the web interface
> and you are prompted at login to create a non-root user that can. We
> did this for security purposes. You can see this in our release notes
> and upgrade notes:
> http://docs.perfsonar.net/manage_update.html#special-upgrade-notes.
> There's a lot of changes in this release so its easy to miss.
>

and in http://docs.perfsonar.net/manage_update.html#special-upgrade-notes

When you upgrade from a version of the software older than version 3.4,
you may be asked to create a new user to login to the web interface. This
is because any user in wheel (e.g. root) is no longer allowed to access
the web interface. Given this new constraint, if none of your existing
users can login to the web interface you will be prompted to create a new
one the first time you login as root. See Managing Users for more information.


My experience with one upgrade install is that I did have a non-root user
account that I frequently used to access the web interface on the 3.3.2
box, but I could not login to the web administrator interface post-install
with that user/password.

I had to run /opt/perfsonar_ps/toolkit/scripts/nptoolkit-configure.py,
delete that user, and then add that user, and answer yes to the "Should
this user be able to login to the web interface?" prompt.

After that, I was able to use that account to login to the web interface.

PeterG

- --
Peter Gutierrez IT/Network Services U. Massachusetts Amherst
Voice: 413 545 1606 PGP: 0xE1668A41

A: Because it interrupts the logical flow of discourse
Q: Why is top posting bad?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlQ1j2wACgkQPTwtHOFmikHE4QCdHImErYKpp/hNBKIpEI8hmJuU
geUAoLTcAWUjJs2nIKPLhDTvmcHoan1Y
=PQEq
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.16.

Top of Page