Get Security Configuration API
Introduced 1.0
The Get Security Configuration API retrieves the current security configuration. This configuration includes authentication domains and other security-related configurations.
Endpoints
GET /_plugins/_security/api/securityconfig
Example request
GET /_plugins/_security/api/securityconfig
Example response
{
"config": {
"dynamic": {
"authc": {
"basic_internal_auth_domain": {
"http_enabled": true,
"transport_enabled": true,
"order": 0,
"http_authenticator": {
"challenge": true,
"type": "basic",
"config": {}
},
"authentication_backend": {
"type": "internal",
"config": {}
}
}
},
"authz": {
"roles_from_myldap": {
"http_enabled": true,
"transport_enabled": true,
"authorization_backend": {
"type": "ldap",
"config": {
"roles_search_filter": "(uniqueMember={0})",
"host": "ldap.example.com",
"port": 389
}
}
}
},
"multi_rolespan_enabled": true,
"hosts_resolver_mode": "ip-only",
"do_not_fail_on_forbidden": false
}
}
}
Response body fields
The response body is a JSON object with the following fields.
Property | Data type | Description |
---|---|---|
config | Object | The root object containing the security configuration. |
Response body fields: config
config
is a JSON object that contains the following fields.
Property | Data type | Description |
---|---|---|
dynamic | Object | The main configuration object containing all security configuration settings. Includes authentication domains (authc ), authorization settings (authz ), and various security behaviors. |
Usage notes
The Get Configuration API provides a way to inspect the current security configuration. When using the API, remember the following usage notes:
-
Read-only operation: This API only retrieves the configuration and does not modify it.
-
Access control: Access to this API should be restricted to administrators because the configuration contains sensitive information about your security setup.
Security considerations
The security configuration contains sensitive information about your authentication mechanisms, LDAP settings, and security policies. Consider the following security best practices:
- Be cautious about storing or logging the output from this API, as it may contain sensitive configuration details.
- Use HTTPS/TLS when interacting with this API to prevent information disclosure.
Permissions
Any users with roles defined in plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
have access to this API.