KaapanaFed: Possibility to change token of local instance in frontend
In FL experiments it may happen that unwanted db objects are dangling around in the backend. Since there is not proper way to fetch them and delete them, a possibility to resolve that issue is to delete the postgres-database. However, this deletes also the local kaapana instance which is after redeployment re-created with a new random token.
When this happens in real-world FL experiments, it's supper annoying to ask every partner to update the instance token of out instance at their site in the Instance Overview. That's why it woudld be desirable to just modify the own token to the one which was used already before and the connection can be re-established without tedious communication to the sites.