Add assertions for not including password fields
What does this MR do and why?
This MR adds 2 assertions around the api response from integration endpoints that check that no password fields are present on the response. This will help ensure sensitive data is not leaked from the api.
Describe in detail what your merge request does and why.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.