The design choice has been to have a (strong) layer enforced by the MQTT broker for every module belonging to the same house and second (weaker) layer to handle users within the same house implemented within the application.
- This avoids creating a new MQTT user for every new user in the house since eGeoffrey has no access to MQTT configuration
- allow implementing additional capabilities delegating to e.g. house admin users complete control over their user base, setting/resetting passwords etc.
- Despite users' security is enforced only at the application layer, this is still only related to the isolated house
Each module connecting to message bus has to know at least the gateway location and optionally how to authenticate against it. This means the authentication and authorization logic lives outside eGeoffrey since it is in charge of the message bus.
- Since eGeoffrey's main use case is when deployed in a secure, controlled environment (e.g. local LAN), by default no authentication is enforced
- Each module authenticates against MQTT using the
house_idas username and an optional password
- all the modules share the same credentials to allow ease of use but still maximum isolation between houses
- For an open MQTT broker with no restrictions, authentication works in the same way (username/password is not enforced by the broker)
- An admin interested in hosting multiple houses has to configure a new user in MQTT only once when a new house is added
- Advanced users can configure the MQTT broker to enforce authentication with username/password, client certificate or client_id prefix. All of those are supported by eGeoffrey
- by default no ACL is enforced; however eGeoffrey's SDK silently discard any message whose recipient is a different house the one is taking care of
- An admin interested in isolating multiple houses running on the same broker can enforce a single, simple ACL which will restrict access based on username (e.g. the house_id):
pattern readwrite egeoffrey/+/%u/#
- By default, modules connect to the gateway over an insecure websocket connection over port 443/tcp
- If you need to ensure confdentiality of the data transmitted by the modules to the gateway, either enable SSL to the websocket listener or make them connecting to the secure MQTTS port 8883/tcp. To do so, set in your
This is referring to users operating within the same house accessing the web GUI.
- the web gui tries first to connect to the MQTT broker residing at the URL the user is visiting without authentication (the default). If it fails (broker elsewhere? username/password required?) shows up a login page requesting the user the gateway hostname, port, house_id, house passocde and, username and password.
- The latter (username and password) are stored in the
gui/users.ymlconfiguration file. Password is not secured (clear-text) since this is belonging to the weaker layer of security and authentication is happening on the client side.
- Users can be managed entirely from within the eGeoffrey web interface.
- By default the following two users are available:
guest / <no password>: guest user (belongs to the `guests group)
admin / admin: admin user (belongs to the
- eGeoffrey defines groups in the
gui/groups.ymlconfiguration file. A user can be part of multiple groups. The following groups are defined but a user can add additional groups:
- guests: can access all the pages of the web interface but the admin pages
- house_admins: can access all the pages of the web interface as well as configure the house, its sensors and rules
- egeoffrey_admins: can access all the pages of the web interface, configure the house and manage eGeoffrey (list installed packages and modules, review logs, access the marketplace, etc)
- Authorization is enforced client-side in the web interface
- admin users can restrict access to individual widgets or entire pages by granting access only to specific groups
- By default, the web gui application connect to the gateway over an insecure websocket connection over port 443/tcp
By design every house is supposed to be hosted on a dedicated Redis database server. Password authentication, if needed, is supported in this configuration.
If MongoDB is used as a backend database, a single database can host multiple houses (this scenario would not be possible with Redis). Authentication with username and password is supported in this configuration. It is up to the admin to provision users to MongoDB, ideally assigning a dbAdmin role only for the assigned database (e.g. the house_id) to the user.