ZEO client authentication utterly unusable

[Darryl Dixon]

For all versions of ZODB tagged to date, the ZEO client authentication option (documented here: http://www.zope.org/Wikis/ZODB/HowtoRunAZEOServer/howto.html) that is present in ZEO.ClientStorage.ClientStorage is unusable.
This is for a variety of reasons, including:
1) zeopasswd.py is needlessly difficult to use as it is not usable as a script (needs "if __name__ == '__main__': main(sys.argv[1:])" added, along with chmod +x etc)
2) ZODB/component.xml is missing the schema definitions for the 'username' and 'password' keys required to use authentication from the client (ironically 'realm' is present, though)
3) ZODB.config.ZEOClient does not pass through username and password credentials even if they are supplied in the config and accepted by the schema
4) The entire end-to-end process required is undocumented (eg, steps to create zeo password database, configuration directives required in zope.conf, etc).

[Christian Theune (ctheune)]

Wichert has been doping something on this, I'll assign this to him for now.

[Wichert Akkerman (wichert)]

1 is not a bug: You need to look at ZEO.scripts.zeopasswd if you want to use a raw script. The egg console_script entry point taks care of the necessary wrapping as well, so if you install ZEO using zc.recipe.egg or using easy_install you will automatically get a working zeopasswd script

I have fixed 2 and 3 in ZODB trunk and the 3.7 and 3.8 branches.

[Darryl Dixon (esrever-otua)]

This is still unfixed in the latest 2.10.6 release.

[Wichert Akkerman (wichert)]

There is no ZODB 2.10.6 release, so I am assuming that you are talking about Zope2.

Zope2 can not get this fix until a new ZODB 3.7 release is made, which is something I can not do.