Thanks to Andrew(s), OpenChange Schema works again

[Andrew Bartlett]

On Tue, 2009-01-06 at 13:35 +0100, Julien Kerihuel wrote:
> On Tue, 2009-01-06 at 11:37 +0200, Sassy Natan wrote:
> > run make;make install, make provision-install, make mapiproxy-install,
> > make installman, make install-server.
> 
> Hi Sassy,
> 
> I've updated the Makefile recently (r972) so mapiproxy-servers-install
> now installs openchange python scripts and ldif file. 
> 
> You should only have to run 'make; make install' to have OpenChange
> installed properly.
> 
> > Now I started to provision my site. I don't know why - But i added to
> > create the smb.conf before starting any step. It was workign before
> > but somethig happend.
> 
> Indeed, I encountered similar issue. Jelmer thought the problem was
> fixed (with the samba master git rev we are using), so I suppose this
> issue will automatically be fixed when we update to a more recent Samba
> master revision.
> 
>  
> >  So now I run the provision-backend, provision, add the options
> > required for openchange in the smb.conf
> >        dcerpc_mapiproxy:server = true
> >        dcerpc_mapiproxy:proxy = true
> >         ### Configuration required by mapiproxy ###
> 
> dcerpc_mapiproxy:proxy is not a valid mapiproxy parametric option. If
> you have found such reference in any OpenChange documentation, please
> let me know this is a bug!
> 
> I have started to document OpenChange server mode
> (architecture/option/behavior):
> http://mapiproxy.openchange.org/#server_mode
> 
> 
> > MAPIPROXY server 'exchange_emsmdb' registered
> > MAPIPROXY server 'exchange_nsp' registered
> > MAPIPROXY server 'exchange_ds_rfr' registered
> > MAPIPROXY server mode enabled
> > MAPIPROXY proxy mode disabled
> [...]
> >  the proxy module is disable since it can't bind to the samba4. 
> 
> proxy mode is disabled because you have set dcerpc_mapiproxy:server to
> true.
> 
> > when running the provision script i get the fowling:
> >  
> > DevBox:/usr/share/openchange/setup# ./openchange_provision
> > --username=samba-admin --password=manager11
> > --simple-bind-dn=cn=samba-admin,cn=samba
> > NOTE: This operation can take several minutes
> > [+] Step 1: Register Exchange OIDs
> > [+] Step 2: Add new Exchange classes and attributes to Samba schema
> > Traceback (most recent call last):
> >   File "./openchange_provision", line 53, in <module>
> >     openchange.provision(setup_path, lp, creds,
> > firstorg=opts.firstorg, firstou=opts.firstou)
> >   File "/usr/lib/python2.5/site-packages/openchange/provision.py",
> > line 309, in provision
> >     install_schemas(setup_path, names, lp, creds)
> >   File "/usr/lib/python2.5/site-packages/openchange/provision.py",
> > line 144, in install_schemas
> >     "SCHEMADN": names.schemadn
> >   File "/usr/lib/python2.5/site-packages/samba/provision.py", line
> > 164, in setup_add_ldif
> >     ldb.add_ldif(data)
> >   File "/usr/lib/python2.5/site-packages/samba/__init__.py", line 192,
> > in add_ldif
> >     self.add(msg)
> > _ldb.LdbError: (19, 'LDAP error 19 LDAP_CONSTRAINT_VIOLATION -
> > <entryDN: no user modification allowed> <>')
> > 
> 
> I need to investigate this traceback more closely. I have only been
> doing provisioning test using the default LDB backend, not any external
> LDAP server. This setup being untested so far, I can only assume it
> doesn't work properly yet.

My guess is that for some reason your provision script fills in
'distinguishedName' on objects being added.  This is always incorrect,
but perhaps Samba doesn't check without the LDAP backend. 

(distinguishedName is mapped to OpenLDAP's entryDN)

Andrew Bartlett
-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Red Hat Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20090107/c71ef78e/attachment.bin