You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the intended flow is for modules to set/delete tasks and automation profiles through the Automation and Recommendation Module (see page 20 in doc/thesis.pdf), this can currently be circumvented by interacting with the Data Storage Module directly. It must be ensured that only the Automation and Recommendation Module can tell the Data Storage Module to set or delete tasks and automation profiles, and that all other modules must refer to the Automation and Recommendation Module for this. This may be a hard-coded special case or alternatively, a generic mechanism to restrict certain message types to certain modules could be introduced.
The text was updated successfully, but these errors were encountered:
While the intended flow is for modules to set/delete tasks and automation profiles through the Automation and Recommendation Module (see page 20 in
doc/thesis.pdf
), this can currently be circumvented by interacting with the Data Storage Module directly. It must be ensured that only the Automation and Recommendation Module can tell the Data Storage Module to set or delete tasks and automation profiles, and that all other modules must refer to the Automation and Recommendation Module for this. This may be a hard-coded special case or alternatively, a generic mechanism to restrict certain message types to certain modules could be introduced.The text was updated successfully, but these errors were encountered: