AS AN Architect
I WANT to have a central solution verifying on a business level that the messages received have reached and have been sent by appropriate participants
SO THAT this logic should not be implemented within the service actually saving the message
Acceptance Criteria
The following sender information must match with the content of the appropriate CentOps Admin database table contents maintained by Bürokratt:
[ ] Participant's name
[ ] Abbreviation of the Participant's name
[ ] Static IP where the message was sent from
[ ] Security token
Technical requirements
[ ] sender information is in plain text JSON format
DSL
[ ] Ruuter DSL as a template to validate permissions of a received CentOps message
AS AN Architect I WANT to have a central solution verifying on a business level that the messages received have reached and have been sent by appropriate participants SO THAT this logic should not be implemented within the service actually saving the message
Acceptance Criteria
The following
senderinformation must match with the content of the appropriate CentOps Admin database table contents maintained by Bürokratt:Technical requirements
senderinformation is in plain textJSONformatDSL