Hey Nicke,
let me guess: You are the software tester and QA manager in your
company? ;-)
Yeah, there might be no documentation for a field description. But maybe
this is obvious. Do you know these software products where you open the
help screen and it tells you:
"Description - here you may enter a description for the user".
Many products work this way. And I always disliked it.
Or take the checkbox
"[x] this resolver is editiable"
The documentation might be: "If you click this checkbox, you mark the
resolver as editable."
This is just waste. The documentation needs to explain to you that an
editable resolver means, that privacyIDEA can write into the resolver to
modify user data. So that even users can be managed from within
privacyIDEA. That this is only implemented for SQL at the moment, since
modifying SQL is more straightforward than modifying LDAP or parsing
plain text files...
(of course also privacyIDEA documentation needs improvement. All
documentation does)
Don't get me wrong. I appreciate all feedback and input. Feel free to
either point out other flaws or even do a pull request. Also on
documentation if you think it is worth adding additional chapters.
As far as the easy editable user resolver or recommended password field
is concerned, there is a shell script
privacyidea-create-userdb
which creates an SQLite user DB at /etc/privacyidea/users.sqlite and in
addition created the resolver and realm accordingly.
It instruments the commands
pi-manage resolver create
and
pi-manage realm create
Take a look at it to get an idea, how you could easily create your user
table in any other database.
Kind regards
Cornelius
>
https://groups.google.com/d/msgid/privacyidea/38abd3da-054b-4c37-9483-a83c12ec2861%40googlegroups.com.