You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/dynamic-user-mod.md
+2
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,8 @@ The program must write, on its standard output:
15
15
- an empty string (or no response at all) if the user should not be created/updated
16
16
- or the SFTPGo user, JSON serialized, if you want to create or update the given user
17
17
18
+
Any output of the program on its standard error will be recorded in the SFTPGo logs with sender `pre_login_hook` and level `warn`.
19
+
18
20
If the hook is an HTTP URL then it will be invoked as HTTP POST. The login method, the used protocol and the ip address of the user trying to login are added to the query string, for example `<http_url>?login_method=password&ip=1.2.3.4&protocol=SSH`.
19
21
The request body will contain the user trying to login serialized as JSON. If no modification is needed the HTTP response code must be 204, otherwise the response code must be 200 and the response body a valid SFTPGo user serialized as JSON.
Copy file name to clipboardexpand all lines: docs/external-auth.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The program must write, on its standard output:
21
21
- an empty string, or no response at all, if authentication succeeds and the existing SFTPGo user does not need to be updated. This means that the credentials already stored in SFTPGo must match those used for the current authentication.
22
22
- a user with an empty username if the authentication fails
23
23
24
-
Any output of the program on its standard error will be recorded in the sftpgo logs with sender `external_auth_hook`.
24
+
Any output of the program on its standard error will be recorded in the SFTPGo logs with sender `external_auth_hook` and level `warn`.
25
25
26
26
If the hook is an HTTP URL then it will be invoked as HTTP POST. The request body will contain a JSON serialized struct with the following fields:
0 commit comments