Allow a user to replace their public key on SeattleGENI about clearinghouse HOT 3 CLOSED

Author: justinc
Milestone Geni Portal v2.1 Release deleted

from clearinghouse.

Author: jsamuel
This is a feature that needs to be added to the new seattlegeni.

from clearinghouse.

Author: jsamuel
Fixed in r3099. A new field is added to the Vessel model to indicate that user keys need to be sync'd. When a user changes their key (through the new page added to seattlegeni, either regenerating or uploading their own), the field is changed for all vessels the user has access to in order to indicate the user keys need to changed through the nodemanager to match what we have in the database. The backend has a new thread running that looks for these cases and does a !ChangeUsers call when needed.

It was intentional that I didn't try to do the nodemanager communication in real time when a user changes their key or uploads their key. If you try to do that, you end up with the potential for a bad user experience, especially later on if we add features like allowing a user to give other users access to vessels they've acquired. Regardless of that, I just don't think a user wants to sit there and wait and it still not being a promise that they can see their nodes immediately in seash, for example, because the nodes may not have all advertised yet. And then to top it all off you'd still have to deal with keeping track of node communication failures and go back and update those later. So, I went with the all-in-the-background approach.

from clearinghouse.