Create a mechanism to filter object details
as a short term workaround, we need a mechanism to filter object details. it will be used primarily to remove sensitive credential information from rest responses.
related bugs -
https:/
https:/
Blueprint information
- Status:
- Complete
- Approver:
- Sergey Lukjanov
- Priority:
- Not
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Matthew Farrellee
Related branches
Related bugs
Sprints
Whiteboard
[SL] Matt, we already have some filtering stuff in https:/
Probably it's not enough, but it could be extended.
[SL]: It sounds reasonable to include support to such stuff into the v2 api backing implementation.
[mattf]: the scope of tyhe v2 api should not be expanded, what needs to be done is a separate effort to eliminate storing of credentials
[SL]: The blueprint named "Create a mechanism to filter object details", so, it's not only about filtering credentials. I mean that anyway we're using such filtering and API is the best layer for doing it. I'm not proposing to solve credentials problem with just filtering them.
[mattf]: my mistake, i wasn't detailed enough when filing this bp. i'll update it.
[mattf]: is appears all the bugs mentioned in this bp have been resolved using existing filter mechanisms. this bp is no longer needed.
