Skip to content

Commit b7316d9

Browse files
committed
docs: Update wording for NetAuth configuration (auth_map/storage_map use)
1 parent fd44177 commit b7316d9

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/reference/auth/netauth.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,12 @@ maddy needs to know the Entity ID to use for authentication. It must
77
match the string the user provides for the Local Atom part of their
88
mail address.
99

10-
Note that storage backends conventionally use email addresses. Since
11-
NetAuth recommends *nix compatible usernames, you will need to map the
12-
email identifiers to NetAuth Entity IDs using `auth_map` (see
13-
documentation page for used storage backend).
10+
Note that storage backends conventionally use email addresses. Since NetAuth
11+
recommends *nix compatible usernames. You will need to either map email
12+
identifiers specified by user to NetAuth Entity IDs using `auth_map` in
13+
endpoint.smtp/imap configuration (recommended) or you would need to use
14+
`storage_map` in storage backend configuration to map NetAuth Entity ID
15+
specified by user back to appropriate storage backend account names.
1416

1517
auth.netauth also can be used as a table module. This way you can
1618
check whether the account exists.

0 commit comments

Comments
 (0)