Bug: User management, confirming a new registered user

[wail-abbas]

When the admin confirms a new registered user from the user management page, the status changes to both pending and confirmed and the user will still not able to login as the account is pending.

[kimakan]

It looks like some of this behavior was intended. However, there is still some inconsistency.
There are two authentication workflows in daiquiri, activation and confirmation.

activation : the user must be activated by a manager or admin. For this workflow after the user has registered, the admin ( or manager) should click 'Activate user' in order to activate the user. However, after the activation the user is marked as confirmed. I would expect to see either the badge active or active and confirmed.

Similar behavior for the authentication workflow confirmation. The user is never shown as active even after the admin has activated the user.

[harenk]

the 'active' flag was initially set, after the user got created on the various CRE: Clues, muse, gregor....
This was somehow lost during updates of the python libs etc., and when the creation of users run into other conditions than initially (i.e.more than 10 years ago).
So fixing the inconsistency with a renewed implementations would be very welcome.