#676 setup.pl: 1.2->1.3 migration / users in the users table

closed
Chris Travers
None
5
2012-12-24
2012-11-14
Erik Huelsmann
No

In 1.2, users are defined solely in the "users" table.

In 1.3, users have to be defined at the database level *and* exist in the users table. However, when upgrading from 1.2 to 1.3, the users remain in the users table, but don't get created as database users.

The consequence of the above is that it's not possible to create the "same" users again: when the user is being created, it's already in the database and the procedure fails.

Proposed solution: add a step to setup.pl which asks the admin which users he wants to "migrate" (ie. create database accounts for). These users will get default passwords with 24h validity, just like any other admin-set password. This procedure seems much more user-friendly than the problem that ario (on irc) ran into where he simply can't create the old user names anymore.

Discussion

  • Chris Travers
    Chris Travers
    2012-12-22

    • assigned_to: nobody --> einhverfr
     
  • Chris Travers
    Chris Travers
    2012-12-22

    It is actually much more complex than this. The users table in 1.2 is in a reserved database which tracks user accounts for *all* databases in an installation. In 1.3 each database itself gets its own users and preferences tables.

    So what I expect to do for 1.3.27 is to migrate user info in, with random passwords, and the will document that one will need to log in post-upgrade and assign passwords.

     
  • Chris Travers
    Chris Travers
    2012-12-22

    I am currently testing a fix for this.

     
  • Chris Travers
    Chris Travers
    2012-12-24

    • status: open --> closed
     
  • Chris Travers
    Chris Travers
    2012-12-24

    rev 5401