Properties for WMS services

The following Properties have been identified as relevant for interaction with WMS:
WMSAdmin: people responsible for administration of WMS + WMS Server through certain Agents
ProductionUser: allow to do Production Management activities
GenericPilotUser: Can Match and Run jobs from any user
PilotUser: Can Match and Run jobs (only his own jobs either individual or group if submitted under a group)
PlainUser: Can Submit Jobs, will execute the Job on the WN and can interact up to certain extend with them.

- JobManager:
  * submitJob/killJob: PlainUser
  * rescheduleJob: PilotUser, WMSAdmin
  * deleteJob/resetJob: WMSAdmin
- JobMonitoring: (to be review in depth)

- I/O Sandbox:
  * fromClient: PlainUser
  * toClient: PilotUser/PlainUser
  * removeSandbox: WMSAdmin
- JobStateUpdate:
  * setJobStatus/setJobApplicationStatus/setJobParameter: PlainUser (must check ownership, can we be sure that it is running the corresponding job? the matcher should return some token)
  * sendHeartBeat: PilotUser
- Matcher:
  * requestJob: PilotUser/GenericPilotUser (further checks are necessary on the server)
  * checkForJob: (it is not used?)
- Notification:
  * sendMail/sendSMS: WMSAdmin
- Administrator:
  * getSiteMask (should most likely go to Monitoring): PlainUser
  * banSite/allowSite/(clearMask): ProductionUser
  * setJobForPilot/setPilotBenchMark: PilotUser (must check ownership, use the token from the matcher)
  * getJobPilotOutput: PlainUser
  * getPilotOutput: ProductionUser/WMSAdmin (with different scope)
  * getPilots: ProductionUser/WMSAdmin (with different scope)
  * getPilotSummary: ProductionUser/WMSAdmin (with different scope)