User story #2862
closed
rudder-users.xml : better example
Added by Francois BAYART about 12 years ago.
Updated about 12 years ago.
Description
It will be fine if you include the same examples in rudder-users.xml as in your online documentation for custom authorizations.
i.e. this line :
<user name="custom" password="custom" role="node_read,node_write,configuration_read,rule_read,rule_edit,directive_read,technique_read"
and I'm not sure but I think the default file (not mine) rudder-users.xml contain hashed password after the upgrade but the <authorication> tag is without hash=md5 or another hash type.
- Tracker changed from Question to User story
- Category set to Documentation
- Status changed from New to 2
- Assignee set to Vincent MEMBRÉ
- Priority changed from N/A to 2
- Target version changed from 18 to 2.4.0~rc1
Vincent, can you look into this please?
- Tracker changed from User story to Question
You're right, rudder-users.xml needs more examples.
I'm going to add some more.
Besides, default users password should not be hashed, I'll look into this.
- Tracker changed from Question to User story
- Tracker changed from User story to Question
- Assignee changed from Vincent MEMBRÉ to Francois BAYART
I completed documentation in rudder-users.xml.
I can't reproduce the case you reported about hashed passwords.
Here's what you should have in rudder-users.xml (and what i got after several migration) :
<authentication>
<user name="jon.doe" password="secret" role="administrator" />
<user name="alex.bar" password="secret2" role="read_only"/>
(documentation)
</authentication>
So instead of "secret" and "secret2" you got hashed passwords and attribute hash not determined??
Have you modified rudder-users before migrating ?
default rudder-users.xml should not be different from what i got.
- Tracker changed from Question to User story
- Status changed from 2 to In progress
I can't reproduce the case you reported about hashed passwords.
May be I become crazy with Rudder you know.
Have you modified rudder-users before migrating ?
yes
It's ok for me.
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
- Status changed from Pending technical review to Discussion
- % Done changed from 100 to 50
wrong ticket number in last commit. this is for ticket #2865
- Status changed from Discussion to Released
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by Nicolas PERRON