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

[spaces] missing optional parameter disabledFeatures results in internal error #40014

Closed
psanz-estc opened this issue Jul 1, 2019 · 1 comment · Fixed by #40017
Closed

[spaces] missing optional parameter disabledFeatures results in internal error #40014

psanz-estc opened this issue Jul 1, 2019 · 1 comment · Fixed by #40017
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@psanz-estc
Copy link

Kibana version: 7.2

Elasticsearch version: 7.2

Describe the bug:
When creating a space via Kibana Space API, if disabledFeatures is not defined, the space is created properly, but ML and stack monitoring tabs won’t work…

According to the doc, disabledFeatures is not required so it should not have any impact on the behavior:
disabledFeatures (string array) Optional list of features that are disabled for the space. Use the Features API to get a list of available features IDs.

Steps to reproduce:

  1. Create the space via API
curl -X POST  -u elastic:password https://192.168.100.100/api/spaces/space -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d'
{
"id": "marketing",
"name": "Marketing",
"description" : "This is the Marketing Space",
"color": "#aabbcc",
"initials": "MK"
}'
  1. In the browser, check the monitoring site: https://192.168.100.100/s/marketing/app/monitoring

  2. Kibana returns: {"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred"}

Expected behavior:
Since disabledFeatures is optinal, space is supposed to work as designed even if the field is not there.

Any additional context:
As a workaround, the spaces can be created with disabledFeatures set to an empty array and it works fine

@psanz-estc psanz-estc added bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature labels Jul 1, 2019
@legrego legrego added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Jul 1, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants