Yes, it is bad form to answer ones own questions, but ... I had not read the documentation carefully. The answer is that the specifications for targets is
user:[EMAIL PROTECTED]:port/path-to-ZSyncer-instance and is as elegant as it gets. It uses Basic Authentication and is documented in the README I neglected to read as this is the fifth version of ZSyncer I've installed and I thought I knew the product. On Wed, 1 Feb 2006, Dennis Allison wrote: > Paul, > > Just moved all our systems to ZSyncer 0.7.0 and have encountered a > problem related to authentication. > > In our past setup, using ZSyncer 0.5.1, we use the ability to specify > a user:password to provide a single authorization mechanism that could be > used by all of our developers. > > Now we've stumbled onto the fact that ZSyncer 0.7.0 has eliminated the > optin al user:password specification. Some of our users can use ZSyncer > and others cannot. It's not clear what authorization is being used -- I > suspect it is ownership, but I have not investigated. > > So, how do I configure things to allow a subset of my developers to use > ZSyncer transparently? > > > > _______________________________________________ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > -- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
