You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
Updates the following functions in the Rules Client to re-use the API key in context and avoid having the system invalidate them when no longer in use:
bulk_delete
bulk_edit
clone
create
delete
update
update_api_key
Also adds a new field to the rule SO to help determine when whether an api key was created by a user or created by us.
doakalexi
changed the title
Updating rules client to allow users with api key auth to manage rules
[ResponseOps] Allow users authenticated with an API keys to manage alerting rules
Mar 28, 2023
[job][logs] Jest Tests #7 / bulkEdit() actions operations should set timeframe in alertsFilter null if doesn't exist
[job][logs] Jest Integration Tests #1 / checking migration metadata changes on all registered SO types detecting migration related changes in registered types
[job][logs] Jest Tests #7 / create() calls the authentication API key function if the user is authenticated using an api key
[job][logs] FTR Configs #22 / detection engine api security and spaces enabled - rule execution logic Threat match type rules terms and match should have the same alerts with pagination
[job][logs] FTR Configs #37 / features Features /api/features with trial license should return a full feature set
[job][logs] FTR Configs #37 / features Features /api/features with trial license should return a full feature set
[job][logs] Jest Tests #7 / MaintenanceWindowClient - active should log and return false is an error is thrown
[job][logs] Jest Tests #7 / MaintenanceWindowClient - update should call update with the correct parameters
[job][logs] FTR Configs #7 / security (basic license) Privileges GET /api/security/privileges should include sub-feature privileges when respectlicenseLevel is false
[job][logs] FTR Configs #7 / security (basic license) Privileges GET /api/security/privileges should include sub-feature privileges when respectlicenseLevel is false
[job][logs] FTR Configs #7 / security (basic license) Privileges GET /api/security/privileges should return a privilege map with all known privileges, without actions
[job][logs] FTR Configs #7 / security (basic license) Privileges GET /api/security/privileges should return a privilege map with all known privileges, without actions
[job][logs] FTR Configs #52 / security Privileges GET /api/security/privileges should return a privilege map with all known privileges, without actions
[job][logs] FTR Configs #52 / security Privileges GET /api/security/privileges should return a privilege map with all known privileges, without actions
[job][logs] FTR Configs #52 / security Privileges GET /api/security/privileges?respectLicenseLevel=false should return a privilege map with all known privileges, without actions
[job][logs] FTR Configs #52 / security Privileges GET /api/security/privileges?respectLicenseLevel=false should return a privilege map with all known privileges, without actions
[job][logs] Jest Integration Tests #2 / SO type registrations does not remove types from registrations without updating excludeOnUpgradeQuery
Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.
Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.
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.
Summary
Updates the following functions in the Rules Client to re-use the API key in context and avoid having the system invalidate them when no longer in use:
Also adds a new field to the rule SO to help determine when whether an api key was created by a user or created by us.
Checklist
To verify