Commit 2c56143b authored by Juliusz Chroboczek's avatar Juliusz Chroboczek

Fix description of wildcard-user in README.

Thanks to J.-J. Sarton.
parent 21e63dcc
...@@ -286,9 +286,9 @@ even Unix passwords). ...@@ -286,9 +286,9 @@ even Unix passwords).
When password authorisation is used, authorised usernames and password are When password authorisation is used, authorised usernames and password are
defined directly in the group configuration file, in the `users` and defined directly in the group configuration file, in the `users` and
`fallback-users` entries. The `users` entry is a dictionary that maps `wildcard-user` entries. The `users` entry is a dictionary that maps user
user names to user descriptions; the `fallback-users` is a list of user names to user descriptions; the `wildcard-user` is a user description
descriptions that are used with usernames that don't appear in `users`. that is used with usernames that don't appear in `users`.
Every user description is a dictionary with fields `password` and Every user description is a dictionary with fields `password` and
`permissions`. The `password` field may be a literal password string, or `permissions`. The `password` field may be a literal password string, or
...@@ -304,13 +304,12 @@ For example, the entry ...@@ -304,13 +304,12 @@ For example, the entry
specifies that user "jch" may login as operator with password "1234", while specifies that user "jch" may login as operator with password "1234", while
"fallback-users": [{"password": "1234", "permissions": "present"}] "wildcard-user": {"password": "1234", "permissions": "present"}
allows any username with password *1234*. Finally, allows any username with password *1234*. Finally,
"fallback-users": [ "wallback-user":
{"password": {"type": "wildcard"}, "permissions": "present"} {"password": {"type": "wildcard"}, "permissions": "present"}
]
allows any username with any password. allows any username with any password.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment