Project

General

Profile

Actions

Architecture #6710

closed

Allow rudder-users.xml based local users to change password

Added by Janos Mattyasovszky over 9 years ago. Updated 7 months ago.

Status:
Resolved
Priority:
4
Category:
Web - Maintenance
Effort required:
Name check:
Fix check:
Regression:
No

Description

Please create a GUI-Based "Change Password" for locally (not LDAP) defined users.

Actions #1

Updated by Dennis Cabooter over 9 years ago

Even better... why not adding, editing and removing users in the gui, instead of using rudder-users.xml? :-)

Actions #2

Updated by Janos Mattyasovszky over 9 years ago

I would be more then happy, just make sure it can be done automatically, as there is currently no authorization according to nested LDAP (AD) group membership, so we had to cook up a small perl script that loops through nested groups and builds an xml file according to the user included, and if there was a change, it restarts jetty, but this is quite some PITA, as then all user sessions are gone, so this can only be done by hand or at night...

Actions #3

Updated by Matthieu CERDA over 9 years ago

  • Assignee set to François ARMAND
  • Priority changed from N/A to 4

Thank you folks !

Assigning this ticket to FAR for dispatching.

Actions #4

Updated by Benoît PECCATTE over 8 years ago

  • Target version set to 4.0.0~rc2
Actions #5

Updated by François ARMAND about 8 years ago

  • Target version changed from 4.0.0~rc2 to 4.1.0~beta1
Actions #6

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Actions #7

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Actions #8

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Actions #9

Updated by François ARMAND almost 8 years ago

  • Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Actions #10

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Actions #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Actions #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Actions #13

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Actions #14

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0~rc2 to 4.2.0
Actions #15

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0 to 4.2.1
Actions #16

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.1 to 4.2.2
Actions #17

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.2 to 4.2.3
Actions #18

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.2.3 to 4.2.4
Actions #19

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.2.4 to 4.2.5
Actions #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.5 to 4.2.6
Actions #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.6 to 4.2.7
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.7 to 414
Actions #23

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 414 to Ideas (not version specific)
Actions #24

Updated by François ARMAND 7 months ago

  • Status changed from New to Resolved
  • Regression set to No

Since that old time, we added a user management plugin that does these kind of things.

And we don't really care anymore of updating user password, because now that's likely the IdP problem.

Actions

Also available in: Atom PDF