Skip to content

[Fleet]: Able to access Fleet Server policy in Default space when policy is created and available in Secondary space only. #193149

Description

Kibana Build details:

VERSION: 8.16.0
BUILD: 78301
COMMIT: 4773f525586a05e58ca82cffaa66c89c7b0df4c1

Preconditions:

  1. 8.16.0 or above Kibana should be available.
  2. Agent Policy should be created.

Steps to reproduce:

  1. Log into the Secondary Space.
  2. Click Add Fleet Server and add all the required URL etc.
  3. Observe Fleet Server policy is created and is accessible on in Secondary Space.
  4. Now navigate to Default Space.
  5. Navigate to Fleet>Agents>Add Fleet Server.
  6. Click continue.
  7. Observe user is able to access same Fleet server policy and the URL is also added under Fleet Settings.

Expected Result:
Fleet Server policy should not be accessible in Default space when policy is created and available in Secondary space only.

Screen Recording:

Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2024-09-17.17-06-03.mp4

Feature:
https://github.com/elastic/ingest-dev/issues/1664

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Team:FleetTeam label for Observability Data Collection Fleet teambugFixes for quality problems that affect the customer experienceimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions