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

Migrate System API to New Platform Core #48957

Closed
joshdover opened this issue Oct 22, 2019 · 2 comments
Closed

Migrate System API to New Platform Core #48957

joshdover opened this issue Oct 22, 2019 · 2 comments
Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

In the legacy platform we have the concept of a "system API" that does not need to be checked for auth access.

Legacy code:

  • src/legacy/core_plugins/kibana/server/lib/system_api.js
  • src/legacy/ui/public/system_api/system_api.js

This should be migrated to the new platform, probably as part of Core rather than the kibana plugin.

I'd expect the client-side core.http service to have a isSystemRequest flag to include the headers on the request.
@joshdover joshdover added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Oct 22, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@joshdover
Copy link
Contributor Author

Duplicate of #43970

@joshdover joshdover marked this as a duplicate of #43970 Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshdover @elasticmachine