Skip to content

[9.3] [Write restricted dashboards] Implements upsert for types supporting access control (#247941)#249503

Merged
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-247941
Jan 19, 2026
Merged

[9.3] [Write restricted dashboards] Implements upsert for types supporting access control (#247941)#249503
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-247941

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

…access control (elastic#247941)

Closes elastic#239686

## Summary

This PR implements the "upsert" case for types supporting access control
in the Saved Objects update operation. The default access mode is always
used during an upsert. The active user profile becomes the owner. If
there is no active user profile, no access control metadata is saved
during the upsert.

### Tests

-
x-pack/platform/test/spaces_api_integration/access_control_objects/apis/spaces/access_control_objects.ts
    - 'should apply defaults when upserting a supported type'
- 'should not write access control metadata when upserting unsupported
types'
- 'should not write access control metadata when upserting a supported
type if there is no active user profile ID'

Note: "upserting" is not supported in bulk update.

---------

Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com>
(cherry picked from commit 7975d47)
@kibanamachine kibanamachine force-pushed the backport/9.3/pr-247941 branch from 6eb0706 to 58fa3de Compare January 19, 2026 07:58
@kibanamachine kibanamachine merged commit 9b0f63d into elastic:9.3 Jan 19, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants