5. Limitations#
To ensure a smooth operation of the OX Connector app on UCS, you as administrator need to know the following limitations.
5.1. Integration of OX Connector and OX App Suite app#
Starting with version 2.1.2, Univention supports the use of the OX Connector for the OX App Suite app from Univention App Center. The OX Connector handles the provisioning, while the OX App Suite delivers the actual groupware.
However, the OX Connector needs administrative credentials to create context objects in the database for the OX App Suite. The installation process doesn’t know these credentials. Therefore, you need to verify the configuration of the OX Connector after you have successfully installed OX App Suite. The reconfiguration runs automatically if, and only if, both apps locate on the same UCS system.
If not,
you find the password in the file /etc/ox-secrets/master.secret
on the UCS system running OX App Suite.
The username of the administrative account is oxadminmaster.
You need to set the credentials in the app settings of the OX Connecor,
see Configuration.
5.2. How the Connector handles faulty items#
The OX Connector knows two strategies how to handle faulty items it can’t synchronize. You can choose which strategy to use: App Settings.
5.2.1. OX Connector continues after faulty items#
When the OX Connector encounters a faulty queue item that it can’t process, it continues with the next queue items. The OX Connector puts the faulty item aside for the Administrator to examine at a later stage. The problem is written in the log file, see Log files.
The app ships a CLI to manage the list of errors, see CLI to monitor the current state.
As administrator, you need to monitor the list of errors manually and decide what to do (delete or retry). Meanwhile, the OX Connector continues to process data it gets from the Listener.
Note that certain errors are excluded from that behavior. When the OX
Connector encounters a problem that hints to a network error, it retries this
one task over and over again as continuing will most probably result in the
same error for all items anyway. Synchronizing objects from the UDM module
oxmail/oxcontext will also be retried as these objects are extremely
important to be in sync. All following items in the queue will likely fail,
therefore the app does not just continue in this case. The strategy of stopping
instead of continuing is also described in the next chapter
OX Connector stops at faulty items.
5.2.2. OX Connector stops at faulty items#
When the OX Connector encounters a faulty queue item that it can’t process, it stops the provisioning at the item and the problematic task in the Listener Converter log file, see Log files.
Despite the stop, the Listener continues to add items to the queue. After the administrator removed the faulty queue item, the Listener Converter continues to process the queue and also takes care of the added items.
As administrator, you need to resolve that conflict manually when it happens, see Provisioning stops working. After the conflict resolution, the connector continues to process the provisioning queue.
5.3. No plausibility validation in access profile rights#
The OX Connector app doesn’t evaluate permission level for created access profiles and tries to create any access profile.
For more information, see OX App Suite Permission Level.