Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 1.95 KB

File metadata and controls

23 lines (18 loc) · 1.95 KB

LdapOutpostConfig

Properties

Name Type Description Notes
pk i32 [readonly]
name String
base_dn Option<String> DN under which objects are accessible. [optional]
bind_flow_slug String
application_slug String Prioritise backchannel slug over direct application slug [readonly]
search_group Option<uuid::Uuid> Users in this group can do search queries. If not set, every user can execute search queries. [optional]
certificate Option<uuid::Uuid> [optional]
tls_server_name Option<String> [optional]
uid_start_number Option<i32> The start for uidNumbers, this number is added to the user.pk to make sure that the numbers aren't too low for POSIX users. Default is 2000 to ensure that we don't collide with local users uidNumber [optional]
gid_start_number Option<i32> The start for gidNumbers, this number is added to a number generated from the group.pk to make sure that the numbers aren't too low for POSIX groups. Default is 4000 to ensure that we don't collide with local groups or users primary groups gidNumber [optional]
search_mode Option<models::LdapapiAccessMode> [optional]
bind_mode Option<models::LdapapiAccessMode> [optional]
mfa_support Option<bool> When enabled, code-based multi-factor authentication can be used by appending a semicolon and the TOTP code to the password. This should only be enabled if all users that will bind to this provider have a TOTP device configured, as otherwise a password may incorrectly be rejected if it contains a semicolon. [optional]

[Back to Model list] [Back to API list] [Back to README]