Background:
The ATKIN Client being agnostic to the message sent, creates potential security risks, as any query could be potentially pulled into an institution and executed.
Requirement:
The AKTIN client should be extended to allow the configuration of a media type validation, so that for example an incoming query is insured to be a valid json or xml.
The media type validation should be independent of the BROKER_REQUEST_MEDIATYPE as this allows the validation against broader types (like for example validating a application/sq+json againg application/json)
Background: The ATKIN Client being agnostic to the message sent, creates potential security risks, as any query could be potentially pulled into an institution and executed.
Requirement: The AKTIN client should be extended to allow the configuration of a media type validation, so that for example an incoming query is insured to be a valid json or xml. The media type validation should be independent of the BROKER_REQUEST_MEDIATYPE as this allows the validation against broader types (like for example validating a application/sq+json againg application/json)