Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add fleet-user creation check #47566
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
base: main
Are you sure you want to change the base?
Add fleet-user creation check #47566
Changes from all commits
a6a254bFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Add persistence verification for the API-only forbidden request.
The admin endpoint test (lines 5176-5178) verifies the forbidden user was not persisted, but the API-only endpoint test has no equivalent check. While both funnel through the same authorization layer, asymmetric verification weakens regression protection.
✅ Add a persistence check after the API-only request
If the
createAPIOnlyUserRequestincludes an email or if API-only users can be queried by name, add a verification similar to lines 5176-5178:s.DoJSON("POST", "/api/latest/fleet/users/api_only", createAPIOnlyUserRequest{ Name: new(t.Name() + "_crossteam_api"), Fleets: &[]fleetsPayload{ {ID: team1.ID, Role: fleet.RoleAdmin}, {ID: team2.ID, Role: fleet.RoleAdmin}, }, }, http.StatusForbidden, &resp) + + // Verify the forbidden API-only request also didn't persist a user. + // Adjust the query method based on how API-only users can be retrieved. + _, err = s.ds.UserByEmail(ctx, t.Name()+"_crossteam_api@example.com") + require.True(t, fleet.IsNotFound(err))Note: Adjust the verification method if API-only users don't have email addresses or require a different lookup mechanism.
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.