Issues with synchronization
If individual users have not been synchronized or are considered orphaned, they were not found in the synchronization process.
Please make sure that these users have filled in all mandatory fields. The mandatory fields are the fields specified in COYO in the "User" tab of the user directory under "Attributes for". The profile fields are optional.
When you can't identify a problem here you can try to set the same settings as in COYO in a LDAP browser to verify your settings and see what COYO sees.
For Mac OS and Ubuntu we recommend the commend-line based LDAP browser ldapsearch.
Please make sure that these users have filled in all mandatory fields. The mandatory fields are the fields specified in COYO in the "User" tab of the user directory under "Attributes for". The profile fields are optional.
When you can't identify a problem here you can try to set the same settings as in COYO in a LDAP browser to verify your settings and see what COYO sees.
For Mac OS and Ubuntu we recommend the commend-line based LDAP browser ldapsearch.
Search afterwards with exactly the settings, which were also used in COYO. Below you will find the command for the tool ldapsearch. Execute this command e.g. on the COYO host.
Without SSL:
Without SSL:
ldapsearch -h "<Hostname>" -p <Port> -D "<Benutzername>" -w "<Passwort>" -b "<Basis DN>" "<Filter des Benutzer-Objekts (optional)>"With SSL:
ldapsearch -H "ldaps://<Hostname>:<Port>" -D "<Benutzername>" -w "<Passwort>" -b "<Basis DN>" "<Filter des Benutzer-Objekts (optional)>"If you use the same settings as in COYO, then you should see the same users here as in COYO. So if your missing user appears here filled with all required fields, then this user should be imported/updated at the next sync.
Issues with login
When you can't login with a user of a user directory there could be issues with the connection or configuration.
To check on the connection just edit the user directory in COYO and hit the button "test connection". When there are errors the button will light red and you get a LDAP error message. Because there are so many we suggest to just google it.
When the connection is working we have another suggestion. Maybe the user and the in COYO configured AD domain don't match. To check on this compare the last part of the userPrincipleName with the AD domain you configured in COYO. These have to match. It's also possible to not set an AD domain to match on all domains.
To check on the connection just edit the user directory in COYO and hit the button "test connection". When there are errors the button will light red and you get a LDAP error message. Because there are so many we suggest to just google it.
When the connection is working we have another suggestion. Maybe the user and the in COYO configured AD domain don't match. To check on this compare the last part of the userPrincipleName with the AD domain you configured in COYO. These have to match. It's also possible to not set an AD domain to match on all domains.
Log entries
If you're hosting COYO on your own you can easily access the COYO log messages by Kibana or directly on the COYO host itself.
If you're using our COYO cloud solution, then you could write us a service ticket and we will help you.
If you're using our COYO cloud solution, then you could write us a service ticket and we will help you.
Kibana
URL: https://<COYO_URL>:5601
User: <COYO_MANAGEMENT_USER>
Passwort: <COYO_MANAGEMENT_PASSWORD>
User: <COYO_MANAGEMENT_USER>
Passwort: <COYO_MANAGEMENT_PASSWORD>
You can find the URL, user and password in your .env file.
A log file can also be found directly in the main directory:
A log file can also be found directly in the main directory:
<COYO_DATA_STORAGE>/backend/logs/coyo-backend.logThen start the sync process and watch the log. Here you will see messages like that an email is already assigned or that mandatory fields are not filled.
