Skip CSRF protection in Generic Alerts Endpoint
What does this MR do?
Skip CSRF protection in the Generic Alerts Endpoint, because public API endpoints doesn't need to have CSRF protection. The endpoint already uses Bearer token based authorization.
This is a part of the Generic Alerts Endpoint feature.
Does this MR meet the acceptance criteria?
Conformity
- [-]
Changelog entry - [-]
Documentation created/updated or follow-up review issue created -
Code review guidelines - [-]
Merge request performance guidelines -
Style guides - [-]
Database guides - [-]
Separation of EE specific content
Performance and Testing
- [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
-
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Peter Leitzen