Skip to content

Document plugins.security.restapi.max_string_length setting - #12989

Open
DarshitChanpura wants to merge 1 commit into
opensearch-project:mainfrom
DarshitChanpura:add-restapi-max-string-length-setting
Open

Document plugins.security.restapi.max_string_length setting#12989
DarshitChanpura wants to merge 1 commit into
opensearch-project:mainfrom
DarshitChanpura:add-restapi-max-string-length-setting

Conversation

@DarshitChanpura

Copy link
Copy Markdown
Member

Description

Documents the new plugins.security.restapi.max_string_length setting, which makes the Security plugin's REST API request body string-length limit configurable (default 4096).

Background: opensearch-security 3.8.0.0 introduced a hard-coded 256-character limit on every string value in a Security REST API request body, which broke legitimate configurations with large free-form values such as document-level security (DLS) queries (opensearch-project/security#6434). The code change replaces that hard limit with this configurable setting (opensearch-project/security#6437).

Added under _security/configuration/yaml.mdopensearch.yml as a new "REST API request body validation" subsection, next to the existing REST API password settings.

Issues Resolved

Documentation follow-up for opensearch-project/security#6434 / opensearch-project/security#6437.

Version

Targets the release that ships opensearch-project/security#6437 (3.9.0, with a planned backport to a 3.8 patch). Maintainers: please advise if this should be labeled for a specific version branch.

Checklist

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developer Certificate of Origin.

For any changes to documentation, I have reviewed the OpenSearch Project style guidelines.

Adds documentation for the new configurable REST API request body string
length limit (default 4096) introduced in opensearch-project/security#6437,
which supersedes the previously hard-coded 256-character limit.

Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
@github-actions

Copy link
Copy Markdown

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference).

@github-actions github-actions Bot added the Tech review PR: Tech review in progress label Aug 28, 2026
@kolchfa-aws kolchfa-aws added release-notes PR: Include this PR in the automated release notes v3.9.0 labels Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-notes PR: Include this PR in the automated release notes Tech review PR: Tech review in progress v3.9.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants