dhis2-devs team mailing list archive

[Calle Hedberg <calle.hedberg@xxxxxxxxx>]

Hi

Definitely agree that "normal" users, who have been working on the database
over a period of time, should be deactivated and not deleted.

BUT you do get the occasional user which were added either as part of
training or added by mistake. The database administrator/superuser should
be able to relatively easily remove such users - he/she CAN of course
delete them directly in the database in any case (assuming full access),
but it's time-consuming AND it requires direct manipulation of the database
which we ideally want to minimize.

In our case here in SA, leaving such users is not really an option, since
the Auditor General would flag that as a security risk (they are requesting
a list of all users with supporting documentation proving that their
credentials have been vetted etc).

In theory we could assume that no temporary user is ever added (for
training or in error), but experience shows we simply don't have that level
of control and discipline at all times (e.g. in this case it was the
academy trainer ismail that we needed to delete again).

Regards
Calle

On 9 April 2015 at 12:05, Lars Helge Øverland <larshelge@xxxxxxxxx>
wrote:

> This is confirmed/knows. The underlying problem is that almost all
> tables in the system have a foreign key to users due to the sharing
> solution, hence we need to check all of them before deleting. One could
> argue that users should not be deleted, rather deactivated, since you
> don't want to lose the history of actions which the user has performed,
> such as creating meta-data, saving data values, etc (i.e. one type of
> "attack" would be to create a user, modify lots of data and then delete
> the user, hence removing all traces of who made the additions). Will
> think some more about this.
>
> ** Changed in: dhis2
>        Status: New => Confirmed
>
> ** Changed in: dhis2
>     Milestone: None => 2.20
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1442042
>
> Title:
>   Unable to delete users who had a chart
>
> Status in DHIS 2:
>   Confirmed
>
> Bug description:
>   Deleting a user who had designed one chart as part of a training
>   exercise did not work (user was superuser). The UI provided no clues -
>   the "progress bar" just continued ad infinitum.
>
>   Had to inspect the server tomcat log to identify what caused the
>   block, then use pgremote to look up the userid, inspect the chart
>   table to identify the linked chart, and the remove or modify it.
>
>   The ideal fix for this would be
>   (a) notify user that the person to be deleted have existing charts;
>   (b) allow user to either delete those charts or to transfer them to
> another user.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dhis2/+bug/1442042/+subscriptions
>


--

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19274

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1442042

Title:
  Unable to delete users who had a chart

Status in DHIS 2:
  Confirmed

Bug description:
  Deleting a user who had designed one chart as part of a training
  exercise did not work (user was superuser). The UI provided no clues -
  the "progress bar" just continued ad infinitum.

  Had to inspect the server tomcat log to identify what caused the
  block, then use pgremote to look up the userid, inspect the chart
  table to identify the linked chart, and the remove or modify it.

  The ideal fix for this would be
  (a) notify user that the person to be deleted have existing charts;
  (b) allow user to either delete those charts or to transfer them to another user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1442042/+subscriptions