No it’s not a school environment, it’s a relative new single server UCS installation.
Here’s the requested output:
root@dc1:~# udm settings/extended_attribute list --filter cn=UniventionPasswordSelfServiceEmail
cn=UniventionPasswordSelfServiceEmail
DN: cn=UniventionPasswordSelfServiceEmail,cn=custom attributes,cn=univention,dc=ldap,dc=domain,dc=com
CLIName: PasswordRecoveryEmail
copyable: None
default: None
deleteObjectClass: 0
disableUDMWeb: None
doNotSearch: 0
fullWidth: 1
groupName: None
groupPosition: None
hook: None
ldapMapping: univentionPasswordSelfServiceEmail
longDescription: During the password recovery process an e-mail is sent to the specified e-mail address. Password recovery via e-mail is only available for users if configured and enabled by the administrator.
mayChange: 1
module: users/user
multivalue: 0
name: UniventionPasswordSelfServiceEmail
notEditable: 0
objectClass: univentionPasswordSelfService
overwritePosition: None
overwriteTab: 0
shortDescription: E-mail address
syntax: emailAddress
tabAdvanced: 0
tabName: Password recovery
tabPosition: None
translationLongDescription: de_DE: An diese E-Mail-Adresse wird während der Passwort-Wiederherstellung eine Mail verschickt. Der Mail-Versand steht dem Benutzer nur zur Verfügung, wenn dieser vom Administrator eingerichtet und freigeschaltet wurde.
translationShortDescription: de_DE: E-Mail-Adresse
translationTabName: de_DE: Passwort-Wiederherstellung
valueRequired: 0
version: 2
okay, that looks just like mine.
Has a user template been created, or is there one?
Let’s start with this output: univention-ldapsearch -b cn=templates,cn=univention,$(ucr get ldap/base) dn
I have this one from the self service: udm settings/usertemplate list --filter cn=selfserviceregistrationtemplate
For completeness:
Master-180 root@master:~# dpkg -l |grep self
ii univention-self-service 4.0.3-50A~4.4.0.202103191337 all Univention Self Service
ii univention-self-service-invitation 4.0.3-50A~4.4.0.202103191337 all Invitation module for Univention Self Service.
ii univention-self-service-master 4.0.3-50A~4.4.0.202103191337 all Univention Self Service
ii univention-self-service-passwordreset-umc 4.0.3-50A~4.4.0.202103191337 all Password reset module for Univention Self Service.
root@dc1:~# dpkg -l |grep self
ii univention-self-service 4.0.3-50A~4.4.0.202103191337 all Univention Self Service
ii univention-self-service-invitation 4.0.3-50A~4.4.0.202103191337 all Invitation module for Univention Self Service.
ii univention-self-service-master 4.0.3-50A~4.4.0.202103191337 all Univention Self Service
ii univention-self-service-passwordreset-umc 4.0.3-50A~4.4.0.202103191337 all Password reset module for Univention Self Service.
lets step back.
The error occurs ins the UMC when a user tries to change the contact data via self-service, or if the Administrator changes the contact data in the UMC for the user.
I am a little bit confused because the error is shown in the passwordreset.log. I would expect that in the m-c-web-server.log, because it is not a password reset.
So it is possible to make the changes for the user via udm, or does the same error occure?
ucr get self-service/ldap_attributes
jpegPhoto,telephoneNumber,roomNumber,departmentNumber,st,homePhone,mobile,homePostalAddress
ucr get self-service/udm_attributes
jpegPhoto,phone,roomnumber,departmentNumber,country,homeTelephoneNumber,mobileTelephoneNumber,homePostalAddress
univention-check-join-status
Joined successfully
the message “Undefined attribute type” is reported by the underlying OpenLDAP library: error.c#L60.
and the meaning of the placeholder is, that it is reported, if an attribute is unknown: LDAP_UNDEFINED_TYPE
It seems that when modifying the attribute “univentionPasswordSelfServiceEmail” and its content, the Schema definition is unknown to OpenLDAP. Please double check that
the Schema file is present on all servers /var/lib/univention-ldap/local-schema/self-service-passwordreset.schema, otherwise reinstall the self-service app
“self-service-passwordreset.schema” is included in /etc/ldap/slapd.conf, otherwise type ucr commit /etc/ldap/slapd.conf and restart the ldap service
The schema file was in fact missing.
However, reinstalling the app did not resolve that. I just copied the file from another installation and put it in that directory. Is this alright or could this cause issues?
The commit on the slapd.conf then added the mentioned schema-file and after restarting the slapd setting the e-mail address works.
