﷽
[Array] Managed clients are clients that server already knows some information about. This speeds up connection, makes it secure and most of all helps to personalize your log files. Managed clients can be rest assured that no one else can have access to their logs or their keys etc.
Setting up managed clients can be very handy in many situations and is highly recommended. For example, consider following managed client object
{
"client_id": "muflihun.com-web-client",
"public_key": "$RESIDUE_HOME/public/muflihun.com-web-client.pem",
"key_size": 128,
"loggers": [
"muflihun.com-general",
"muflihun.com-security",
"muflihun.com-business"
],
"default_logger": "muflihun.com-general",
"user": "abumusamq"
}
This is a complete managed client (i.e, all the necessary as well as optional fields are filled up).
- Server will know that it's expecting a connection from client with ID
muflihun.com-web-client - When the connection comes it simply has to be
connect me to muflihun.com-web-client - Server will then make connection and encrypt this connection using previously provided
public_keyi.e,muflihun.com-web-client.pem - Server will generate 128-bit key
- Any logs associated to this client will automatically have ownership assigned to
abumusamqwithRW-R-----permissions (subject tofile_modeconfig) - Listed loggers are expected loggers (more loggers may be allowed but if you use more loggers we recommend you to add it to this list) - if you use resitail it will pick up loggers from this list
- Any unmanaged loggers associated to this client will have configurations from
default_logger's configuration