[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: invalid value for syntax

* Quanah Gibson-Mount (quanah@stanford.edu) [040707 18:35]:
> it is an integer syntax.  So I would assume that for uid=tvm, there is an 
> integer attribute that has an non-integer value.
> I find the following attributes using that syntax (there are more), but 
> what immediately jumps out is there is no value's for:
> sambalogontime or sambapwdcanchange, both of which are required to be 
> integers
> >dn: uid=tvm,ou=People,dc=skole,dc=skolelinux,dc=no
> >loginshell: /bin/bash
> >objectclass: shadowaccount
> >objectclass: imapuser
> >objectclass: posixaccount
> >objectclass: top
> >objectclass: sambasamaccount
> >sambalogofftime: 2147483647
> >sambaacctflags: [UX         ]
> >creatorsname: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no
> >userpassword:: e2NyeXB0ffg8TnE1VG1eRGZMdDY=
> >cn:: TXlocmUsIFRvcmJqw7hybiBWLg==
> >sambalogontime:

yes, this is one of the culprits

> >modifiersname: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no
> >mailmessagestore: /var/lib/maildirs/tvm
> >sambantpassword: 6926B99BA325C703D3F90BA1885022CD
> >sambasid: S-1-5-21-872698249-1279178062-3287419353-42424
> >sambapwdcanchange:

and this is the other. 

> >gidnumber: 20712
> >sambapwdmustchange: 2147483647
> >homedirectory: /skole/tjener/home1/tvm
> >uid: tvm
> >sambalmpassword: F34EBD4864ACAEE775DA33E02F3D2D43
> >sambaprimarygroupsid: S-1-5-21-872698249-1279178062-3287419353-42425
> >uidnumber: 20712
> >modifytimestamp: 20031006075030Z
> >sambapwdlastset: 1065426630
> >sambakickofftime: 2147483647
> >createtimestamp: 20030826065934Z
> >displayname:: TXlocmUsIFRvcmJqw7hybiBWLg==

adding a random integer here fixes that slapadd problem.

debian runs a perl script (fix_ldif) over the 2.0 ldifs, which
adds some necessary object classes etc, attempting to fix the
gravest problems. 

for this problem class at hand it would be best to check if
attributes conform to their syntax definition. how could i do
that in perl? i would need to find the syntax for each attribute
(easily done by parsing the used schemas) and then check what
each cryptic number means and if the string following the
attribute name conforms to that definition. This is the part which
i have no clue how to accomplish it. is this feasable in the
first place? Hints? has this been done before?

the ugly simple solution would be to add a number to those two
attributes if they are empty...