Reorder revoke-token from API integration test - #37696
Merged
jotacarma90 merged 1 commit intoJul 17, 2026
Merged
jotacarma90 merged 1 commit into
jotacarma90 merged 1 commit into
Conversation
Member
Verification 🟢The 4.x API integration suite is executed by Jenkins from the wazuh-qa-automation copy of the tests, so the revoke reorder was verified there via the equivalent change (wazuh/wazuh-qa-automation#8183) — build #4:
🟢 SUCCESS (Test files 2/0, individual tests 45/0). This PR keeps the wazuh/wazuh copy of the test in sync with the same reorder. |
jotacarma90
approved these changes
Jul 17, 2026
jotacarma90
deleted the
enhancement/37677-api-integration-revoke-token-and-remove-wazuh-dbd
branch
July 17, 2026 11:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
test_security_PUT_endpoints.tavern.yamlrunsPUT /security/user/revokeas the 4th of 9 test blocks. Revoking invalidates the sharedtest_login_token, so every stage that reuses it afterwards (DELETE /security/user/authenticate,PUT /security/users/{user_id},.../run_as,PUT /security/config,PUT /security/configCheck) fails with401 Invalid tokenonce strict auth validation landed in 4.14.7 (#37034). The equivalent fix was applied on main/5.0.0 in #35040 (move revoke to the end) but was never backported to 4.14.x.Proposed Changes
PUT /security/user/revokeblock to the end ofapi/test/integration/test_security_PUT_endpoints.tavern.yaml, afterPUT /security/config (Check), matching the ordering already in place on main/5.0.0 since API ITs order changed to revoke token at last #35040.Review Checklist
Closes #37677
Closes #37676