Skip to content
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

Jump to bottom

Non-interactive sessions leveraging the http auth provider should have their profiles activated #158277

Open
legrego opened this issue May 23, 2023 · 2 comments
Open

Non-interactive sessions leveraging the http auth provider should have their profiles activated #158277

legrego opened this issue May 23, 2023 · 2 comments
Labels
enhancement New value added to drive a business result Feature:Security/User Profile NeededFor:Alerting Services NeededFor:Dashboard NeededFor:ResponseOps NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases NeededFor:SharedUX Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@legrego
Copy link
Member

legrego commented May 23, 2023 •
edited by azasypkin
Loading

We currently do not activate user profiles for accounts leveraging the http auth provider (e.g. passing an Authorization header to Kibana via reverse proxy).

We should allow these accounts to have their profiles activated, so they can take advantage of profile-related features. We will need to be careful about this implementation, as we do not want to blindly activate user profiles on any API call to Kibana. We will need to be thoughtful about when & where we decide to perform this activation step.

Required by: #167459
@legrego legrego added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! enhancement New value added to drive a business result Feature:Security/User Profile labels May 23, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego legrego mentioned this issue May 23, 2023
Open
@azasypkin azasypkin changed the title Interactive sessions leveraging the http auth provider should have their profiles activated Non-interactive sessions leveraging the http auth provider should have their profiles activated Jan 17, 2024
@azasypkin azasypkin mentioned this issue Jan 29, 2024
Open
@SiddharthMantri SiddharthMantri mentioned this issue Jun 19, 2024
Closed
@nickpeihl
Copy link
Member

nickpeihl commented Oct 16, 2024 •
edited
Loading

I believe we have another use case that will need profiles on the http auth provider level. Since Saved Objects APIs are now deprecated, the @elastic/kibana-presentation team is working on a domain level CRUD API for Dashboards. #179344 added the created_by property to saved objects such as Dashboards. However, this field can not be populated when submitting a create operation using the API, so we can not identify a Dashboard owner if/when we have object level permissions.

cc @teresaalvarezsoler @thomasneirynck

@thomasneirynck thomasneirynck mentioned this issue Oct 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Security/User Profile NeededFor:Alerting Services NeededFor:Dashboard NeededFor:ResponseOps NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases NeededFor:SharedUX Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nickpeihl @azasypkin @legrego @Dosant @elasticmachine