Ticket #42 (closed Bug report: fixed)

Opened 3 years ago

Last modified 11 months ago

Node cannot be renamed

Reported by: max-horvath Assigned to: fproulx
Priority: normal Milestone: WifiDog Auth Server 1.0
Component: Auth server, Other Keywords:
Cc:

Description (Last modified by benoitg) 

As long as a user has been assigned as technical officer to a node, 
the node cannot be renamed. Also you cannot rename the node after 
removing the user from the technical officer role. Only after deleting 
the entry manually in the table node_stakeholders you can rename a 
node.

Attachments

Change History

12/26/05 20:48:09 changed by fproulx

  • status changed from assigned to closed.
Logged In: YES 
user_id=1245118

I added a foreign key constraint ON UPDATE CASCADE ON DELETE CASCADE to 
node_stakeholders table

02/28/06 13:12:11 changed by max-horvath

  • status changed from closed to reopened.
  • version changed from None to Auth Server SVN.
  • resolution deleted.
  • description changed.
  • milestone set to WifiDog Auth Server 1.0.

02/28/06 13:12:27 changed by max-horvath

  • status changed from reopened to new.
  • owner changed from nobody to fproulx.

02/28/06 13:12:38 changed by max-horvath

  • status changed from new to closed.
  • resolution set to fixed.

10/23/06 06:02:52 changed by freechelmi

  • status changed from closed to reopened.
  • resolution deleted.

I repoen it because this problem occurs in another situation, If a node has juste been created and the technical officer and proprietary assigned, Those users cannot put the new Node Name in their nodes.

Only admins can Do it.

BTW I think that the NodeID should be also changeable by the proprietary and technical officer.

12/07/06 21:06:08 changed by benoitg

  • description changed.

Access control for Nodes is currently a mess, and waiting on the role system #162 for a cleanup.

However, not allowing owner to rename a node was done on purpose (we agree it should be a Network preference, and it's for this sort of flexibility that we need #162).

01/21/08 13:54:48 changed by benoitg

  • status changed from reopened to closed.
  • resolution set to fixed.

Fixed in [1324]

Add/Change #42 (Node cannot be renamed)




Action