Skip to content

Add known issue for role mappings file bug #112504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 4, 2024
Merged

Add known issue for role mappings file bug #112504

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
04eac0d
Add known issue for role mappings file bug
thecoop Sep 4, 2024
e9021db
Update URL syntax
thecoop Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/reference/release-notes/8.15.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ memory lock feature (issue: {es-issue}111847[#111847])
<<api-conventions-number-values,incorrectly>> assume that this value will be within a particular range (e.g. that it fits into a 32-bit
signed integer) may encounter errors (issue: {es-issue}111854[#111854])

* Elasticsearch will not start if custom role mappings are configured using the
`xpack.security.authc.realms.*.files.role_mapping` configuration option. As a workaround, custom role mappings
can be configured using the [REST API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-role-mapping.html) (issue: {es-issue}112503[#112503])

[[breaking-8.15.0]]
[float]
=== Breaking changes
Expand Down
Loading