providers_ldap_update
PUT/providers/ldap/:id/
LDAPProvider Viewset
Request
Path Parameters
A unique integer value identifying this LDAP Provider.
- application/json
Body
required
Possible values: non-empty
Flow used for authentication when the associated application is accessed by an un-authenticated user.
Flow used when authorizing this provider.
Flow used ending the session from a provider.
DN under which objects are accessible.
Possible values: non-empty
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
Possible values: >= -2147483648
and <= 2147483647
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
Possible values: >= -2147483648
and <= 2147483647
Possible values: [direct
, cached
]
Possible values: [direct
, cached
]
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.
Responses
- 200
- 400
- 403
- application/json
- Schema
- Example (from schema)
Schema
Flow used for authentication when the associated application is accessed by an un-authenticated user.
Flow used when authorizing this provider.
Flow used ending the session from a provider.
Get object component so that we know how to edit the object
Internal application name, used in URLs.
Application's display Name.
Internal application name, used in URLs.
Application's display Name.
Return object's verbose_name
Return object's plural verbose_name
Return internal model name
DN under which objects are accessible.
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
Possible values: >= -2147483648
and <= 2147483647
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
Possible values: >= -2147483648
and <= 2147483647
Possible values: [direct
, cached
]
Possible values: [direct
, cached
]
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.
{
"pk": 0,
"name": "string",
"authentication_flow": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"authorization_flow": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"invalidation_flow": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"property_mappings": [
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
],
"component": "string",
"assigned_application_slug": "string",
"assigned_application_name": "string",
"assigned_backchannel_application_slug": "string",
"assigned_backchannel_application_name": "string",
"verbose_name": "string",
"verbose_name_plural": "string",
"meta_model_name": "string",
"base_dn": "string",
"certificate": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"tls_server_name": "string",
"uid_start_number": 0,
"gid_start_number": 0,
"outpost_set": [
"string"
],
"search_mode": "direct",
"bind_mode": "direct",
"mfa_support": true
}
- application/json
- Schema
- Example (from schema)
Schema
Validation Error
{
"non_field_errors": [
"string"
],
"code": "string"
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "string",
"code": "string"
}