[Interop] online testing environment
Brad Fitzpatrick
brad at danga.com
Fri Jan 19 15:29:22 CST 2007
On Fri, 19 Jan 2007, Peter Saint-Andre wrote:
> b. Client developers (and for that matter server developers) will
> register at a website like https://interop.xmpp.org/ (no, that doesn't
> exist yet). They will choose a preferred username to be set up at each
> server instance. That way a given developer on, say, the Psi project
> will be able to log in as psidev at ejabberd.interop.xmpp.org and so on.
> We'll need to figure out some algorithm for password creation.
>
> 4. Make it secure. All connections (c2s and s2s) will be protected via
> TLS. To make that easier, the XSF will issue certificates (both domain
> and, in the future, end-user) through its intermediate certification
> authority. Only authorized users (registered as above) will be allowed
> to use the system. No in-band registration. Etc.
Then how do we do interop testing of s2s with Dialback, if we're only
using TLS? I propose every server run both:
djabber.ssl.interop.xmpp.org
djabber.cleartext.interop.xmpp.org
Then we can force all interactions of SSL-vs-not between any two products.
Or how do we test client<->server in-band registration? (admittedly much
less of an issue than the TLS one...)
- Brad
More information about the Interop
mailing list