FSM Settings Created an FSM Tree DCS TRACKER

FSM Settings ❚Created an FSM Tree: ❚ DCS ❙ TRACKER ❘TRACKER_LV � DUs ❘TRACKER_HV � TRACKER_HV_P 1 ❘DUs � TRACKER_HV_P 2 ❘DUs ❙ MUON ❘MUON_LV ❘MUON_HV Clara Gaspar, March 2006 1

Access Control Settings ❚Using Access Control Toolbar, created: ❙Domains ❘TRACKER, TRACKER_HV, MUON, DCS ❙Groups ❘TRACKER_OPERATOR, TRACKER_EXPERT, MUON_OPERATOR, DCS_OPERATOR � <domain>_OPERATOR has privileges: <domain>: Control � TRACKER_EXPERT has privideges: ❘TRACKER: <all> and TRACKER_HV: <all> ❙Users ❘Tracker. Op, Tracker. Exp, Muon. Op, Dcs. Op (Could be: John, Mary, etc. ) Clara Gaspar, March 2006 2

FSM Tree Access Control ❚A CU can require a certain privilege level “Domain: Privilege” for: ❙a) Operating, b) Sending Expert actions ❘Privileges can be: Monitor, Control, Debug, Modify ❚Tree Access Control Settings ❚ DCS ❙ TRACKER ❘TRACKER_LV ❘TRACKER_HV ❙ MUON ❘MUON_LV ❘MUON_HV DCS: Control TRACKER: Debug MUON: Control Clara Gaspar, March 2006 DCS: Debug TRACKER: Debug MUON: Control 3

FSM Access Control Choices ❚Some remarks: ❙When the logged in user changes: ❘A callback gets called (twice: “NO USER” first). ❘If any trees were taken they are “Released” ❘Each panel takes into account the new privileges Clara Gaspar, March 2006 4

Access Control Tool ❚Comments: ❙When creating a User it gets “disabled” by default. I always “fell” here… ❙Monitor, Control, Debug, Modify ❘Not very meaningful (for Expert actions)… ❙How does it synchronize across systems? Clara Gaspar, March 2006 5