ssoosshd ldap probe
Runs the login path’s directory lookup and field resolution against the configured server, and stops before the write. It reports the filter it actually sent, every attribute the directory returned rather than only the ones the configuration names, what each configured field resolved to, and which group values the allowlist would discard.
Nothing is written: no directory record, no group rows, no miss window, no auto-disable. The database is not opened at all.
The connection comes from the config file and cannot be overridden here, for the same reason it cannot be in the web console: the point is to test the configuration you are about to run, not a different one.
Synopsis
Section titled “Synopsis”ssoosshd ldap probe [flags] [args]Options
Section titled “Options”| Flag | Type | Default | Description |
|---|---|---|---|
--attributes |
stringSlice | attributes to request; empty asks for every user attribute | |
--email |
string | value for {{.Email}} in the filter | |
--extra |
stringArray | value for {{.Extra.<name>}}, as name=value (repeatable) | |
--filter |
string | filter to run; empty uses the configured ldap.user_filter | |
--json |
bool | false |
print the result as JSON |
--literal |
bool | false |
send –filter exactly as typed, interpolating and escaping nothing |
--subject |
string | value for {{.Subject}} in the filter | |
--username |
string | value for {{.Username}} in the filter |
Global options
Section titled “Global options”Inherited from ssoosshd and its parents.
| Flag | Type | Default | Description |
|---|---|---|---|
-c, --config |
string | path to the ssoosshd config file |