new: Add config option user_org_uuid_in_response_header, allowing to … #9885
Conversation
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
…include a response header with the requesting user's org UUID
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.
…include a response header with the requesting user's org UUID
What does it do?
If enabled, MISP will return a header with the requesting user's org uuid.
This would allow to do some packet inspection / validation, checking sharing group membership of the requesting user on proxy, by only looking at the json response (if/when it includes sharing group definition).
I'm not sure whether a lot of other people would use it, but thought I'd propose a PR anyway.
Questions