Project

General

Profile

Actions

Bug #14326

closed

Regular user don't work when ldap user are declared

Added by Benoît PECCATTE about 5 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
67
Name check:
Fix check:
Regression:

Description

Declare some regular user in rudder-users.xml
Additionnaly declare some ldap user in rudder-users.xml

Regular user cannot connect
Additional user have no right at all

Maybe a documentation is missing on how to do that

Actions #1

Updated by François ARMAND about 5 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #2

Updated by Benoît PECCATTE about 5 years ago

  • Subject changed from Regular user don'twork when ldap user are declared to Regular user don't work when ldap user are declared
  • Category set to Web - Config management
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32
Actions #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions #4

Updated by François ARMAND almost 5 years ago

  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • Priority changed from 32 to 50

I'm upgrading to "major". It may be disruptive (for ex if ldap is down => no workaround whereas it was supposed to be able to have one).

Actions #5

Updated by François ARMAND almost 5 years ago

  • Effort required set to Very Small
  • Priority changed from 50 to 78

I believe it's very small, or at least if not, it's very small to requalify it :)

Actions #6

Updated by François ARMAND almost 5 years ago

  • Assignee set to François ARMAND
Actions #7

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions #8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #9

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 78 to 76
Actions #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 76 to 74
Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 74 to 72
Actions #12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 72 to 70
Actions #13

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 70 to 67
Actions #14

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #15

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #18

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #19

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #20

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #21

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #22

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #23

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #24

Updated by François ARMAND about 2 years ago

  • Status changed from New to Resolved

This is not the case anymore: I can have both user in ldap only, or file only, or both

Actions

Also available in: Atom PDF