[Fleet] Fix agentless integrations incorrect splash screen(s) by Supplementing · Pull Request #264570 · elastic/kibana

Supplementing · 2026-04-21T03:02:58Z

Summary

This PR is a follow up bug fix to #263552

We noticed that after hiding the splash screen, users would still be redirected to another screen insisting they install elastic agent when using an agentless integration, which wasnt correct. This PR fixes that. Additionally, there was a small 'flash' where when the packageInfo was not yet populated, the original splash screen removed in #263552 would render for a split second as the default behavior, this PR also fixes that. The fix is a routing check to skip multiPageLayouts for agentless integrations.

video1457578972.mp4

Testing

Add the following to your kibana.dev.yml file:

xpack.fleet.agentless.customIntegrations.enabled: true
# Emulate cloud + agentless for local testing
xpack.cloud.id: '123456789'
xpack.fleet.agentless.enabled: true
xpack.fleet.agentless.api.url: 'https://api.agentless.url/api/v1/ess'
xpack.fleet.agentless.api.tls.certificate: './config/node.crt'
xpack.fleet.agentless.api.tls.key: './config/node.key'
xpack.fleet.agentless.api.tls.ca: './config/ca.crt'

Then install this custom integration:
custom_okta-3.14.2.zip

cc: @nimarezainia

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Documentation was added for features that require explanation or tutorials
Unit or functional tests were updated or added to match the most common scenarios
If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
Flaky Test Runner was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

See some risk examples
...

…so fixed splash screen flashing (now shows loading when !packageInfo

elasticmachine · 2026-04-21T03:03:03Z

Pinging @elastic/fleet (Team:Fleet)

macroscopeapp · 2026-04-21T03:05:32Z

Approvability

Verdict: Needs human review

This bug fix changes UI routing logic for agentless integrations. All changed files are owned by @elastic/fleet, not the PR author. Additionally, there's an unresolved review comment questioning whether part of the implementation is necessary, which warrants owner review.

^{You can customize Macroscope's approvability policy. Learn more.}

Supplementing · 2026-04-21T14:18:31Z

@elasticmachine merge upstream

…reen

elasticmachine · 2026-04-21T15:36:45Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 739c21d

Failed CI Steps

Test Failures

[job] [logs] Jest Tests #11 / SelectedFilters should render properly
[job] [logs] Fleet Cypress Tests #1 / View agents list Bulk actions should navigate to Maintenance and diagnostics submenu
[job] [logs] Fleet Cypress Tests #1 / View agents list Bulk actions should navigate to Security and removal submenu and show unenroll option
[job] [logs] Fleet Cypress Tests #1 / View agents list Bulk actions should show hierarchical menu with submenus

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`fleet`	2.4MB	2.4MB	+405.0B

History

💔 Build #431022 failed 85fc2d2

jen-huang · 2026-04-21T21:25:21Z

Also, consider backporting this fix. I think the bug has been around for a while unfortunately :(

…uting level and never land there with agentless anyway

jen-huang

Much cleaner now! Ty for the changes, LGTM

kibanamachine · 2026-04-22T18:11:13Z

Starting backport for target branches: 9.3, 9.4

https://github.com/elastic/kibana/actions/runs/24794700970

kibanamachine · 2026-04-22T18:19:58Z

💔 Some backports could not be created

Status	Branch	Result
❌	9.3	Backport failed because of merge conflicts
✅	9.4

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 264570

Questions ?

Please refer to the Backport tool documentation

@nimarezainia

…264570) (#265119) # Backport This will backport the following commits from `main` to `9.4`: - [[Fleet] Fix agentless integrations incorrect splash screen(s) (#264570)](#264570)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  Co-authored-by: Mason Herron <46727170+Supplementing@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@nimarezainia

…c#264570) ## Summary This PR is a follow up bug fix to elastic#263552 We noticed that after hiding the splash screen, users would still be redirected to another screen insisting they install elastic agent when using an agentless integration, which wasnt correct. This PR fixes that. Additionally, there was a small 'flash' where when the packageInfo was not yet populated, the original splash screen removed in elastic#263552 would render for a split second as the default behavior, this PR also fixes that. The fix is a routing check to skip multiPageLayouts for agentless integrations. https://github.com/user-attachments/assets/78e97aa8-494e-444d-bb0b-f3f2c665337e ## Testing Add the following to your kibana.dev.yml file: ``` xpack.fleet.agentless.customIntegrations.enabled: true # Emulate cloud + agentless for local testing xpack.cloud.id: '123456789' xpack.fleet.agentless.enabled: true xpack.fleet.agentless.api.url: 'https://api.agentless.url/api/v1/ess' xpack.fleet.agentless.api.tls.certificate: './config/node.crt' xpack.fleet.agentless.api.tls.key: './config/node.key' xpack.fleet.agentless.api.tls.ca: './config/ca.crt' ``` Then install this custom integration: [custom_okta-3.14.2.zip](https://github.com/user-attachments/files/26917447/custom_okta-3.14.2.zip) cc: @nimarezainia ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@nimarezainia

…c#264570) ## Summary This PR is a follow up bug fix to elastic#263552 We noticed that after hiding the splash screen, users would still be redirected to another screen insisting they install elastic agent when using an agentless integration, which wasnt correct. This PR fixes that. Additionally, there was a small 'flash' where when the packageInfo was not yet populated, the original splash screen removed in elastic#263552 would render for a split second as the default behavior, this PR also fixes that. The fix is a routing check to skip multiPageLayouts for agentless integrations. https://github.com/user-attachments/assets/78e97aa8-494e-444d-bb0b-f3f2c665337e ## Testing Add the following to your kibana.dev.yml file: ``` xpack.fleet.agentless.customIntegrations.enabled: true # Emulate cloud + agentless for local testing xpack.cloud.id: '123456789' xpack.fleet.agentless.enabled: true xpack.fleet.agentless.api.url: 'https://api.agentless.url/api/v1/ess' xpack.fleet.agentless.api.tls.certificate: './config/node.crt' xpack.fleet.agentless.api.tls.key: './config/node.key' xpack.fleet.agentless.api.tls.ca: './config/ca.crt' ``` Then install this custom integration: [custom_okta-3.14.2.zip](https://github.com/user-attachments/files/26917447/custom_okta-3.14.2.zip) cc: @nimarezainia ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@nimarezainia

…c#264570) ## Summary This PR is a follow up bug fix to elastic#263552 We noticed that after hiding the splash screen, users would still be redirected to another screen insisting they install elastic agent when using an agentless integration, which wasnt correct. This PR fixes that. Additionally, there was a small 'flash' where when the packageInfo was not yet populated, the original splash screen removed in elastic#263552 would render for a split second as the default behavior, this PR also fixes that. The fix is a routing check to skip multiPageLayouts for agentless integrations. https://github.com/user-attachments/assets/78e97aa8-494e-444d-bb0b-f3f2c665337e ## Testing Add the following to your kibana.dev.yml file: ``` xpack.fleet.agentless.customIntegrations.enabled: true # Emulate cloud + agentless for local testing xpack.cloud.id: '123456789' xpack.fleet.agentless.enabled: true xpack.fleet.agentless.api.url: 'https://api.agentless.url/api/v1/ess' xpack.fleet.agentless.api.tls.certificate: './config/node.crt' xpack.fleet.agentless.api.tls.key: './config/node.key' xpack.fleet.agentless.api.tls.ca: './config/ca.crt' ``` Then install this custom integration: [custom_okta-3.14.2.zip](https://github.com/user-attachments/files/26917447/custom_okta-3.14.2.zip) cc: @nimarezainia ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@nimarezainia

…c#264570) ## Summary This PR is a follow up bug fix to elastic#263552 We noticed that after hiding the splash screen, users would still be redirected to another screen insisting they install elastic agent when using an agentless integration, which wasnt correct. This PR fixes that. Additionally, there was a small 'flash' where when the packageInfo was not yet populated, the original splash screen removed in elastic#263552 would render for a split second as the default behavior, this PR also fixes that. The fix is a routing check to skip multiPageLayouts for agentless integrations. https://github.com/user-attachments/assets/78e97aa8-494e-444d-bb0b-f3f2c665337e ## Testing Add the following to your kibana.dev.yml file: ``` xpack.fleet.agentless.customIntegrations.enabled: true # Emulate cloud + agentless for local testing xpack.cloud.id: '123456789' xpack.fleet.agentless.enabled: true xpack.fleet.agentless.api.url: 'https://api.agentless.url/api/v1/ess' xpack.fleet.agentless.api.tls.certificate: './config/node.crt' xpack.fleet.agentless.api.tls.key: './config/node.key' xpack.fleet.agentless.api.tls.ca: './config/ca.crt' ``` Then install this custom integration: [custom_okta-3.14.2.zip](https://github.com/user-attachments/files/26917447/custom_okta-3.14.2.zip) cc: @nimarezainia ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

remove incorrect screen showing when using agentless integrations, al…

85fc2d2

…so fixed splash screen flashing (now shows loading when !packageInfo

Supplementing requested a review from a team as a code owner April 21, 2026 03:02

Supplementing added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Fleet Team label for Observability Data Collection Fleet team labels Apr 21, 2026

jen-huang self-requested a review April 21, 2026 05:03

Merge branch 'main' into investigate-and-fix-incorrect-integration-sc…

739c21d

…reen

jen-huang reviewed Apr 21, 2026

View reviewed changes

Comment thread ...lications/fleet/sections/agent_policy/create_package_policy_page/multi_page_layout/index.tsx Outdated

Supplementing added 2 commits April 22, 2026 07:55

removed component level patching, not needed since we check at the ro…

e541a0a

…uting level and never land there with agentless anyway

merge upstream

0a54c51

Supplementing added backport:version Backport to applied version labels v9.3.0 v9.4.0 and removed backport:skip This PR does not require backporting labels Apr 22, 2026

Supplementing requested a review from jen-huang April 22, 2026 17:03

Supplementing enabled auto-merge (squash) April 22, 2026 17:03

jen-huang approved these changes Apr 22, 2026

View reviewed changes

Supplementing merged commit 8752556 into elastic:main Apr 22, 2026
27 checks passed

jen-huang added the v9.5.0 label Apr 22, 2026

kibanamachine mentioned this pull request Apr 22, 2026

[9.4] [Fleet] Fix agentless integrations incorrect splash screen(s) (#264570) #265119

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Fleet] Fix agentless integrations incorrect splash screen(s)#264570

[Fleet] Fix agentless integrations incorrect splash screen(s)#264570
Supplementing merged 4 commits intoelastic:mainfrom
Supplementing:investigate-and-fix-incorrect-integration-screen

Supplementing commented Apr 21, 2026 •

edited by kibanamachine

Loading

Uh oh!

elasticmachine commented Apr 21, 2026

Uh oh!

macroscopeapp Bot commented Apr 21, 2026 •

edited

Loading

Uh oh!

Supplementing commented Apr 21, 2026

Uh oh!

elasticmachine commented Apr 21, 2026

Uh oh!

Uh oh!

jen-huang commented Apr 21, 2026

Uh oh!

jen-huang left a comment

Uh oh!

Uh oh!

kibanamachine commented Apr 22, 2026

Uh oh!

kibanamachine commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

Supplementing commented Apr 21, 2026 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Testing

Checklist

Identify risks

Uh oh!

elasticmachine commented Apr 21, 2026

Uh oh!

macroscopeapp Bot commented Apr 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Approvability

Uh oh!

Supplementing commented Apr 21, 2026

Uh oh!

elasticmachine commented Apr 21, 2026

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

Async chunks

History

Uh oh!

Uh oh!

jen-huang commented Apr 21, 2026

Uh oh!

jen-huang left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Apr 22, 2026

Uh oh!

kibanamachine commented Apr 22, 2026

💔 Some backports could not be created

Manual backport

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Supplementing commented Apr 21, 2026 •

edited by kibanamachine

Loading

macroscopeapp Bot commented Apr 21, 2026 •

edited

Loading