Project

General

Profile

Actions
Copy link

Improvement #1724

closed

Add a mechanism to not lock out a user without consent

Added by liaham over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
liaham
Target version:
0.3.0
Start date:
Due date:
% Done:

100%

Estimated time:
Compatible Redmine Version:
Pull Request Link:

Description

With the fixed bug #1723 it might be that there are users couldn't give consent even if the system was configured to expect the consent. If so those users will be locked out when they try to log in.

We need a mechanism to make sure every registered and active user can log in and give her consent afterwards if it is missing.

This is also important if case an administrator decides at a later point in time when there are already some registered users to require a consent!

Related issues 1 (0 open — 1 closed)

Related to xmera Omnia - Bug #1723: Missing privacy consent on registration and user account pageClosedliaham

Actions
Actions
Copy link
 #1

Updated by liaham over 1 year ago

  • Related to Bug #1723: Missing privacy consent on registration and user account page added
Actions
Copy link
 #2

Updated by liaham over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by liaham over 1 year ago

  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by liaham over 1 year ago

  • Project changed from xmera Omnia to Redmine Legal Notes
  • Category deleted (31)
  • Status changed from In Progress to Closed
  • Target version changed from 4.0.2 to unreleased
  • % Done changed from 0 to 100
  • Affected component deleted (redmine-legal-notes)
Actions
Copy link
 #5

Updated by liaham over 1 year ago

  • Target version changed from unreleased to 0.3.0
Actions
Copy link

Also available in: Atom PDF