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.

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

[security-in-core] Expose authz APIs from Core #183849

Open
legrego opened this issue May 20, 2024 · 1 comment
Open

[security-in-core] Expose authz APIs from Core #183849

legrego opened this issue May 20, 2024 · 1 comment
Labels
Feature:Security/Authorization Platform Security - Authorization Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@legrego
Copy link
Member

legrego commented May 20, 2024

Part of #174578

This issue is about migrating the authz APIs to re-expose them from Core, similar to what was done to authc in #177976

Before we migrate, the @elastic/kibana-security team needs to decide on a preferred API. The current authz API has grown organically, and there are some DX improvements we may consider making before exposing them from Core.

@legrego legrego added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! Feature:Security/Authorization Platform Security - Authorization labels May 20, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Security/Authorization Platform Security - Authorization Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

2 participants