Bug 43429 - usertemplates are broken - syntax does not allow templates
usertemplates are broken - syntax does not allow templates
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks: 39856
  Show dependency treegraph
 
Reported: 2017-01-26 16:12 CET by Philipp Hahn
Modified: 2019-01-03 07:19 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2017-01-26 16:12:55 CET
Task #6641 - UCS Technical training

Several properties use the same syntax as users/user, which don't allow the use of <templates>:

udm settings/usertemplate create --position "cn=templates,cn=univention,$(ucr get ldap/base)" --set name=test --set phone='+49-555-4711-<uidNumber>' --set secretary='uid=<username>,cn=users,$(ucr get ldap/base)'

E: Invalid Syntax: phone: Value must not contain anything other than digits, letters, dots, brackets, slash, plus, or minus!

E: Invalid Syntax: secretary: Not a valid LDAP DN


udm settings/usertemplate create --position "cn=templates,cn=univention,$(ucr get ldap/base)" --set name=test --set displayName='<lastname>, <firstname>' --set disabled=1 --set description='<username>' --set title='<username>' --set organisation='<username>' --set pwdChangeNextLogin=1 --set mailPrimaryAddress="<username>@$(dnsdomainname)" --set mailAlternativeAddress="<firstname>.<lastname>@$(dnsdomainname)" --set e-mail="<lastname>@$(dnsdomainname)" --set phone='+49-555-4711' --set street='<username>' --set postcode='<uidNumber>' --set city='<username>' --set employeeType='<username>' --set departmentNumber='<uidNumber>' --set secretary="cn=Administrator,cn=users,$(ucr get ldap/base)" --set unixhome='/home/<username>' --set shell='/bin/<username>' --set scriptpath='/script/<username>' --set profilepath='/profile/<username>' --set primaryGroup="cn=<username>,cn=groups,$(ucr get ldap/base)" --set groups="cn=<username>,cn=groups,$(ucr get ldap/base)"

# univention-ldapsearch -LLLo ldif-wrap=no -b cn=test,cn=templates,cn=univention,$(ucr get ldap/base) | ldapsearch-decode64 
dn: cn=test,cn=templates,cn=univention,dc=schulung4,dc=ucs
cn: test
sambaProfilePath: /profile/<username>
street: <username>
title: <username>
mailAlternativeAddress: <username>@schulung4.ucs
userDisabledPreset: 1
sambaMungedDial: bQAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABkAAEAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAUAAFABoACAABAEMAdAB4AEMAZgBnAFAAcgBlAHMAZQBuAHQANTUxZTBiYjAYAAgAAQBDAHQAeABDAGYAZwBGAGwAYQBnAHMAMQAwMDAwMDAwMA==
objectClass: top
objectClass: univentionUserTemplate
objectClass: univentionSAMLEnabled
objectClass: univentionObject
postalCode: <uidnumber>
mail: <username>@schulung4.ucs
sambaLogonScript: /script/<username>
userPrimaryGroupPreset: cn=<username>,cn=groups,dc=schulung4,dc=ucs
description: <username>
loginShell: /bin/<username>
univentionObjectType: settings/usertemplate
userPwdMustChangePreset: 1
userGroupsPreset: cn=<username>,cn=groups,dc=schulung4,dc=ucs
telephoneNumber: +49-555-4711
mailPrimaryAddress: <username>@schulung4.ucs
l: <username>
o: <username>
homeDirectory: /home/<username>
secretary: cn=Administrator,cn=users,dc=schulung4,dc=ucs
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:19:38 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.