The AggreGate Server is built as a multi-user server. Ordinarily, one person installs and manages the AggreGate Server itself, and numerous other people use it to access their Device Servers, Devices and other objects like Alerts, Event Filters etc. These users can all belong to the same company, or they can be paying customers who purchase AggreGate Server access from a vendor who installed AggreGate Server on his own servers.
Users access the server through user accounts. Immediately following AggreGate Server installation, only a single account exists in the system, default administrator.
For someone to gain access to AggreGate Server using one of its User Interfaces (AggreGate Client, Web Service, etc), they must be authenticated and authorized by the server. The only operation that does not require prior authentication is self-registration.
|
Related tutorial: Granting One User Access to Objects of Another User |
Ownership
Every user account owns different system objects: Alerts, Widgets etc. The Contexts of all these objects always exist, but a user's permission table may prevent him from accessing his own objects. Objects that are accessible by newly created users are defined by Default User Permissions global AggreGate Serversetting.
Administering Users
