maddy

 1# Native NetAuth
 2
 3maddy supports authentication via NetAuth using direct entity
 4authentication checks.  Passwords are verified by the NetAuth server.
 5
 6maddy needs to know the Entity ID to use for authentication.  It must
 7match the string the user provides for the Local Atom part of their
 8mail address.
 9
10Note that storage backends conventionally use email addresses.  Since
11NetAuth recommends *nix compatible usernames, you will need to map the
12email identifiers to NetAuth Entity IDs using `auth_map` (see
13documentation page for used storage backend).
14
15auth.netauth also can be used as a table module.  This way you can
16check whether the account exists.
17
18Note that the configuration fragment provided below is very sparse.
19This is because NetAuth expects to read most of its common
20configuration values from the system NetAuth config file located at
21`/etc/netauth/config.toml`.
22
23```
24auth.netauth {
25  require_group "maddy-users"
26  debug off
27}
28```
29
30```
31auth.netauth {}
32```
33
34## Configuration directives
35
36### require_group _group_
37
38Optional.
39
40Group that entities must possess to be able to use maddy services.
41This can be used to provide email to just a subset of the entities
42present in NetAuth.
43
44---
45
46### debug `on` | `off`
47
48Default: `off`