![]() ![]() Non-active users are appointed by a specific shell, default /bin/false. In this configuration file the uid range of users wanted in the Kopano server needs to be defined. The default set by this file are usually enough, in-line comments explain each option. All other user properties are done using the normal unix tools.Ī configuration file, /etc/kopano/unix.cfg, exists for this plugin. ![]() The kopano-admin tool has to be used to update these user properties. These properties are the email address, overriding quota settings, and administrator settings. Since the unix files do not contain enough information for Kopano, there are some properties of a user that will be stored in the database. Passwords are checked against /etc/shadow, so the kopano-server process must have read access to this file (this process is normally run as root, so usually that is not a problem). Group information will be read from /etc/group. ![]() The Unix plugin is used on a server which has all its user information setup in the /etc/passwd file. ![]() Newer setups should either use the db plugin or the ldap plugin (recommended). This plugin is mostly delivered for backwards compatibility. Table 4.1. User plugin comparison Feature More information on managing users can be found in User Management.įor a comparison between the different plugins, see the table below: Multi-server support is only supported in the Kopano Enterprise edition. The `ldap` plugin can optionally also hold the required configuration for a multi-server Kopano environment. The ldap plugin is used most in larger setups as it proves to be most flexible and integrates nicely with an organization’s the existing infrastructure. There are three options, namely db, unix and ldap.īy default the db plugin is used as it does not require any further configuration. This setting determines which back-end is used for managing users and groups. Also make sure to give the user enough permissions to connect from localhost to this database, or –if the Kopano server connects over the network to the MySQL database– allow it to connect from the IP-address from which the Kopano Server will connect.įor example the following MySQL statement grants all privileges to user “kopano” with password “password” from localhost:Īnother important configuration option for the Kopano Server is the user_plugin. Make sure that the MySQL user that the Kopano Server uses to connect to the database has all privileges, including the right to create a new database. It will create a database and the tables it needs at first start. The Kopano Server needs a MySQL database to function, and therefor needs to know how to connect to the MySQL server and the authentication credentials for its database. In this chapter we only explain the basic configuration option of Kopano Server. For most setups these defaults will already be fine. If a config option is not present in the configuration file, the default setting will be assumed. Configuring SSL for Windows Mobile and Windows Phone Configure Z-Push (ActiveSync for Mobile Devices) Configure KC Postfix integration with the DB plugin Configure KC Postfix integration with virtual users Configure KC Postfix integration with Active Directory Configure Postfix integration with OpenLDAP Configure Kopano-dagent for delivery via unix socket Configuring Kopano for users stored in LDAP Configuring OpenLDAP to use the Kopano schema Configure Kopano for user management with LDAP (e.g. Using Kopano Konnect to sign into services supporting ID4me Using Kopano Konnect to sign into Nextcloud Configure 3rd Party Applications to Authenticate using Konnect Either should be backed up using your standard backup software. You can set this to be the /Backups folder as it is above, or set it to be an external drive. The most important of these is the backupDestination. PipTitle=”Bender Backup Error on: $macSN” PipPath=”/usr/local/robotcloud/bin/scroobiuspip” LogPath=”/usr/local/robotcloud/logs/bender.log” MacOS=$(sw_vers | awk ‘/ProductVersion/’) If you edit this file, the following settings are available: Note that it calls the /usr/local/robotcloud/bin/bender binary when run at 22:00 every day. Once the installer is complete, you can view the installed LaunchDaemon at /Library/LaunchDaemons/. I’d go ahead and install Bender at the default location, so click Install. Once downloaded, run the package installer.Īt the Welcome to Bender screen, click Continue.Īgree to the licensing agreement by clicking the Continue button.Ĭlick Agree again (assuming of course that you agree to the license).Ĭhoose who you wish to install the software for and click Continue. To do so, we’re going to install a little app called Bender from the great folks at Robot Cloud. Here, we’re going to look at backing up the settings of a macOS Server using Bender. In past versions of this guide, I covered Time Machine Server. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |