-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fixing incorrect error that was being displayed on Share to Spaces flyout #142410
Fixing incorrect error that was being displayed on Share to Spaces flyout #142410
Conversation
… is expected downstream
Pinging @elastic/kibana-security (Team:Security) |
I just tried to spin up this PR an I'm still getting an error:
I'm not sure if I'm doing it correct however. Your instructions in the PR description says to "Login as |
@watson Sorry for the confusion; Ive updated the instructions to better reflect the steps to reproduce and screenshots of the expected results. As for the error you posted: was that on startup or when trying to reproduce this bug? |
I just pulled this down and everything looks good to the eye, but if you open the browser console or network tab you see a 404 for _share_saved_object_permissions when you click the space icon to open the flyout. |
I believe the |
Gotcha. Is this an internal-only way of running ES (sec disabled)? If so, I think this is fine. |
That was when I was trying to see if the bug addressed by this PR was fixed. I.e. when I clicked on one of the spaces icons to open the fly-out. Let's sync IRL today to see what's going on |
Exactly @jeramysoucy - the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason I my initial checkout of the PR was still running the old code, hence why I got the same error. Looks fine now 👍
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
… is expected downstream (elastic#142410) (cherry picked from commit 36b2296)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
… is expected downstream (#142410) (#142638) (cherry picked from commit 36b2296) Co-authored-by: Kurt <[email protected]>
… is expected downstream (elastic#142410)
… is expected downstream (elastic#142410)
Summary
An error was being displayed when ES was started without security enabled. since the downstream code was expecting a
404
instead of the bad request error that was being sent on the response.Steps to reproduce
Login aselastic
Before:
After: