The Java synapse client instance is created/reset with whatever SYNAPSE_AUTH_TOKEN is stored in state. We expect that SAT can eventually be switched during a session, e.g. because a data manager need to switch between different accounts used to manage DCC A vs DCC B. It might be better to use a watcher to initialize/reset the client more reactively when SAT is updated. After all, there wouldn't really be a case when SAT is updated but we don't want to update the client instance right away?
The Java synapse client instance is created/reset with whatever
SYNAPSE_AUTH_TOKENis stored in state. We expect that SAT can eventually be switched during a session, e.g. because a data manager need to switch between different accounts used to manage DCC A vs DCC B. It might be better to use a watcher to initialize/reset the client more reactively when SAT is updated. After all, there wouldn't really be a case when SAT is updated but we don't want to update the client instance right away?