Project

General

Profile

Actions

User story #8549

closed

User Management: Support for rudder variables in password field

Added by Arnaud ANDRE almost 8 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Hello,

Actually, password input in "User management" technique form must be filled with raw value (plain or hashed password).
Could it be possible to support rudder variables in this field (exemple : ${myusers.bob[password]} ) ?

In my use case I need to load user informations with passwords hashed from a json file ("CFEngine variable definition using a JSON file" technique).

Thanks.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #6125: We can define key-values on nodes, but we can't use it in the directivesRejectedFrançois ARMAND2015-01-14Actions
Actions #1

Updated by François ARMAND over 7 years ago

We are in the process of evaluating how to do exactly that.
The mains guiding ideas are:

- add the possibility to use JS as a scripting lang in direcitve parameters so that you can manipulate datas,
- add node contextualized data set available in directive parameters (and technique created with the editor)
- allow the user to enrich available data.
- make these data available also on the node as JSON,

Implementation must take care of privacy (i.e, some data must remains on Rudder server and never go to the node), performance (it is absolutly impossible to have a major system wide performance hit (particulary for generation time and agent execution time) if the feature is not used), consistancies (on langage to access data, on way to provide/remove data set, etc), and life cycle (i.e, we must unconsistencies because some data where updated in a dataset, but not in all the place accessing to it).

So, we are still evaluating the pros/cons and looking for alternatives. As soon as it looks less like a big mazzy fog, we will post on rudder-dev to have user feedback.

Hope it helps,

Actions #2

Updated by François ARMAND over 7 years ago

  • Category changed from Techniques to Web - Config management
Actions #3

Updated by François ARMAND over 7 years ago

  • Related to Bug #6125: We can define key-values on nodes, but we can't use it in the directives added
Actions #4

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.5 to 3.2.6
Actions #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.6 to 3.2.7
Actions #6

Updated by François ARMAND over 7 years ago

The status of this one is much improved with #9057 (allow ${node.properties[...]} expansion in directive parameters) and #8629 (allow javascript in directive parameters).

Is it sufficient to close that ticket ?

Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.7 to 3.2.8
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.8 to 3.2.9
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.9 to 3.2.10
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.2.10 to 3.2.11
Actions #11

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.2.11 to 339
Actions #12

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 339 to 4.0.4
Actions #13

Updated by Benoît PECCATTE about 7 years ago

  • Tracker changed from Bug to User story
Actions #14

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.0.4 to 4.0.5
Actions #15

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.0.5 to 4.0.6
Actions #16

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.0.6 to 4.0.7
Actions #17

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.0.7 to 357
Actions #18

Updated by Alexis Mousset over 6 years ago

  • Target version changed from 357 to 4.1.6
Actions #19

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.8 to 4.1.9
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #23

Updated by Benoît PECCATTE about 6 years ago

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

Updated by Alexis Mousset almost 5 years ago

  • Status changed from New to Rejected

It is very likely enough, closing.

Actions

Also available in: Atom PDF