Infrastructure

Initially only subjects in the Node's Subject list should be able to update the node. This essentially means the update call should come directly from the MN.

May want this to be separate from node list. Anyone can add their own subject to the node list, call updateNodeCapabilities, and since their subject will equal the subject in the updated node list, then they will have control over the node.

Administrators of nodes should go through an approval process, similarly to the way Nodes will be approved.

Should the SubjectList on the Node be updated determined by the subjects present on the node? Seems like an easy way to lose control over the node for a while. So, if a subject needs to change because the former subject has been disabled/changed, our current functionality relies on the new subject equaling the subject in the cert. So, literally anyone who is a valid user can make themselves a subject of a nodelist and control of that node.

Decided this would not be a part of nodeList. rather it will be a property of the LDAP D1Node structure not revealed through the nodelist but managed via the elusive cn administration webpage.

Is this an issue for MN authorization or related to CN adminsitration?