That's very possible. The line with DNS reads:
X509v3 Subject Alternative Name:
DNS:wave.1011ltd.com, DNS:1011ltd.com,
othername:<unsupported>, othername:<unsupported>
Checking on startssl.com, it indicates that I have a certificate for
"wave.1011ltd.com".
Does this mean I should create a new certificate for 1011ltd.com? But
to check, the certificate wiki
(http://code.google.com/p/wave-protocol/wiki/Certificates) indicates
that the "Common Name" should include the "wave.",
Thanks for the help!
On Sun, Jan 31, 2010 at 3:57 PM, Joe Gregorio <[email protected]> wrote:
> Benjamin,
> I tried again and the discover looks good:
>
> <iq type="get" id="9488-1" to="1011ltd.com" from="wave.bitworking.net">
> <query xmlns="http://jabber.org/protocol/disco#items"/>
> </iq>
> Jan 31, 2010 10:13:33 AM
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
> sendPacket
> INFO: key for this error is org.xmpp.packet.IQ:1011ltd.com:9488-1
> Jan 31, 2010 10:13:33 AM
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
> processPacket
> INFO: received XMPP packet:
>
> <iq type="result" to="wave.bitworking.net" from="1011ltd.com" id="9488-1">
> <query xmlns="http://jabber.org/protocol/disco#items";>
> <item jid="search.1011ltd.com" name="User Search"/>
> <item jid="wave.1011ltd.com" name="Google Prototype Wave Server - FedOne"/>
> </query>
> </iq>
>
>
> So that part looks good, and the wave shows up on wavesandbox with all
> three participants, but when I try to add a blip on wavesandbox I get
> the following:
>
> <iq type="set" to="wave.bitworking.net" from="wave.wavesandbox.com"
> id="5808a87c-submit.3-sr">
> <pubsub xmlns="http://jabber.org/protocol/pubsub";>
> <publish node="wavelet">
> <item>
> <submit-request
> xmlns="http://waveprotocol.org/protocol/0.2/waveserver";>
> <delta
> wavelet-name="wave://bitworking.net/w+XvOhcn7wjdBX/conv+root">CkkKGAgHEhSvDx62JmD4XkFvJPHiJ9RS4B31phIaamNncmVnb3Jpb0B3YXZlc2FuZGJveC5jb20aERoPCgtiK201VTFDc2l5QRIAEqcBCoABCm1UxHbB2fOtpj7Y7DjcfaiT4rRLl5ALrB1O2GyMZNvAd9GX52EckEqvsvWOpI2XdscopmP1ThlZEx58b0x8N7Sq7eETfU7ejp+vCJl+qvpHT4v0hug6cl9FWI/eyslGkcvgfhVfLvX4VJD8BPcbvwJ3M7qN4hkYU1ACqbS7o9kSICeNLxl7VajoxsVnJmg0kSdzL6JV+M5dt4PY5rK8PXgPGAE=</delta>
> </submit-request>
> </item>
> </publish>
> </pubsub>
> </iq>
> Jan 31, 2010 10:18:44 AM
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
> processIqPacket
> INFO: key for this error is
> org.xmpp.packet.IQ:wave.wavesandbox.com:5808a87c-submit.3-sr
> Jan 31, 2010 10:18:44 AM
> org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppFederationHost
> processSubmitRequest
> INFO: PSD in submitRequest is delta:
> "\n\030\b\a\022\024\257\017\036\266&`\370^Ao$\361\342\'\324r\340\035\365\246\022\[email protected]\032\021\032\017\n\vb+m5u1csiya\022\000"
> signature {
> signature_bytes:
> "\nmT\304v\301\331\363\255\246>\330\3548\334}\250\223\342\264K\227\220\v\254\035N\330l\214d\333\300w\321\227\347a\034\220J\257\262\365\216\244\215\227v\307(\246c\365N\031Y\023\036|oL|7\264\252\355\341\023}N\336\216\237\257\b\231~\252\372GO\213\364\206\350:r_EX\217\336\312\311F\221\313\340~\025_.\365\370T\220\374\004\367\033\277\002w3\272\215\342\031\030SP\002\251\264\273\243\331"
> signer_id:
> "\'\215/\031{U\250\350\306\305g&h4\221\'s/\242U\370\316]\267\203\330\346\262\274=x\017"
> signature_algorithm: SHA1_RSA
> }
>
> Jan 31, 2010 10:18:44 AM
> org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl
> isLocalWavelet
> INFO: ### WS is local?
> [WaveId:bitworking.net!w+XvOhcn7wjdBX]/[WaveletId:bitworking.net!conv+root]
> = true
> Jan 31, 2010 10:18:44 AM
> org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl
> submitRequest
> WARNING: Submit request: unknown signer. WaveletName:
> [WaveId:bitworking.net!w+XvOhcn7wjdBX]/[WaveletId:bitworking.net!conv+root]delta:
> delta:
> "\n\030\b\a\022\024\257\017\036\266&`\370^Ao$\361\342\'\324r\340\035\365\246\022\[email protected]\032\021\032\017\n\vb+m5u1csiya\022\000"
> signature {
> signature_bytes:
> "\nmT\304v\301\331\363\255\246>\330\3548\334}\250\223\342\264K\227\220\v\254\035N\330l\214d\333\300w\321\227\347a\034\220J\257\262\365\216\244\215\227v\307(\246c\365N\031Y\023\036|oL|7\264\252\355\341\023}N\336\216\237\257\b\231~\252\372GO\213\364\206\350:r_EX\217\336\312\311F\221\313\340~\025_.\365\370T\220\374\004\367\033\277\002w3\272\215\342\031\030SP\002\251\264\273\243\331"
> signer_id:
> "\'\215/\031{U\250\350\306\305g&h4\221\'s/\242U\370\316]\267\203\330\346\262\274=x\017"
> signature_algorithm: SHA1_RSA
> }
>
> org.waveprotocol.wave.crypto.UnknownSignerException: could not find
> information about signer [...@14e113b
> at
> org.waveprotocol.wave.crypto.WaveSignatureVerifier.verify(WaveSignatureVerifier.java:77)
> at
> org.waveprotocol.wave.examples.fedone.waveserver.CertificateManagerImpl.verifySingleSignature(CertificateManagerImpl.java:159)
> at
> org.waveprotocol.wave.examples.fedone.waveserver.CertificateManagerImpl.verifyDelta(CertificateManagerImpl.java:143)
> at
> org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl.submitRequest(WaveServerImpl.java:251)
> at
> org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppFederationHost.processSubmitRequest(XmppFederationHost.java:192)
> at
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent.processPubsubSet(WaveXmppComponent.java:492)
> at
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent.processIqPacket(WaveXmppComponent.java:446)
> at
> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent.processPacket(WaveXmppComponent.java:354)
> at
> org.jivesoftware.whack.ExternalComponent$1.run(ExternalComponent.java:333)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
> Jan 31, 2010 10:18:45 AM
> org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppFederationHost$SubmitResponsePacketListener
> onFailure
> WARNING: submit request to waveserver failed: Unknown signer
>
>
> Note that when I do the same thing, create a wave on bitworking.net and then
> then add [email protected] and [email protected], I can
> successfully add blips on wavesandbox.com and have them show up on my
> console, which
> leads me to believe that this is a certificate issue. Is it possible
> you created the
> certificate for 'wave.1011ltd.com' and not '1011ltd.com'?
>
> What do you see for the values of "DNS:" when you run:
>
> $ openssl x509 -text -in ../certs/1011ltd.com.crt
>
> Thanks,
> -joe
>
> On Sun, Jan 31, 2010 at 8:33 AM, Benjamin Nortier <[email protected]> wrote:
>> Thanks Joe.
>>
>> Coud you try that again? I had OpenFire running when you connected,
>> but not the FedOne component so that would explain why you didn't see
>> the service...
>>
>> Cheers
>> Benjamin
>>
>> On Sun, Jan 31, 2010 at 1:44 AM, Joe Gregorio <[email protected]> wrote:
>>> When I start my FedOne server and then use the client to create
>>> a wave and try to add [email protected] to the wave I see
>>> the following in my FedOne logs:
>>>
>>>
>>> <iq type="get" id="6908-1" to="1011ltd.com" from="wave.bitworking.net">
>>> <query xmlns="http://jabber.org/protocol/disco#items"/>
>>> </iq>
>>> Jan 30, 2010 8:32:27 PM
>>> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
>>> sendPacket
>>> INFO: key for this error is org.xmpp.packet.IQ:1011ltd.com:6908-1
>>> Jan 30, 2010 8:32:29 PM
>>> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
>>> processPacket
>>> INFO: received XMPP packet:
>>>
>>> <iq type="result" to="wave.bitworking.net" from="1011ltd.com" id="6908-1">
>>> <query xmlns="http://jabber.org/protocol/disco#items";>
>>> <item jid="search.1011ltd.com" name="User Search"/>
>>> </query>
>>> </iq>
>>>
>>> In the discovery that's going on your server doesn't list a wave extension
>>> as available via discovery. Compare the response above with the discovery
>>> request and response that happen when I add [email protected]
>>> to the same wave:
>>>
>>> <iq type="get" to="wave.bitworking.net" from="wave.wavesandbox.com"
>>> id="9352-310">
>>> <query xmlns="http://jabber.org/protocol/disco#info"/>
>>> </iq>
>>> Jan 30, 2010 8:37:29 PM
>>> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
>>> processIqPacket
>>> INFO: key for this error is org.xmpp.packet.IQ:wave.wavesandbox.com:9352-310
>>> Jan 30, 2010 8:37:29 PM
>>> org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent
>>> sendPacket
>>> INFO: sent XMPP packet:
>>> <iq type="result" id="9352-310" from="wave.bitworking.net"
>>> to="wave.wavesandbox.com">
>>> <query xmlns="http://jabber.org/protocol/disco#info";>
>>> <identity category="collaboration" type="google-wave" name="Google
>>> Prototype Wave Server - FedOne"/>
>>> <feature var="http://waveprotocol.org/protocol/0.2/waveserver"/>
>>> </query>
>>> </iq>
>>>
>>> Double check the configuration options for OpenFire, particularly
>>> the section about configurations for the Wave extension:
>>>
>>> http://code.google.com/p/wave-protocol/wiki/OpenFireInstallation
>>>
>>> Thanks,
>>> -joe
>>>
>>> --
>>> Joe Gregorio
>>> Developer Relations, Google Wave
>>>
>>>
>>>
>>> On Fri, Jan 29, 2010 at 2:20 PM, [email protected]
>>> <[email protected]> wrote:
>>>> Hi
>>>>
>>>> My wave federation setup is (I hope) almost working, but there are
>>>> some problems which I think are related.
>>>>
>>>> Here's the scenario:
>>>> 1. The wave server is running on 1011ltd.com, connected to Openfire
>>>> 2. I create a new wave in the sandbox and add '[email protected]'
>>>> to the wave.... no incoming messages in the open server console.
>>>> 3. I create a new wave in the sandbox and add 'bjnort...@wave.
>>>> 1011ltd.com' to the wave... and I can see the incoming deltas.
>>>>
>>>> I should be able to add someone from the sandbox without the 'wave.'
>>>> bit, correct?
>>>>
>>>> Then there's some weird interaction if I have the console running as
>>>> user 'bjnortier'. When I create a wave in the sandbox and add
>>>> '[email protected]', nothing happens in the console, but when I
>>>> also add '[email protected]', the wave shows up in the
>>>> console and I can reply. The user that has replied shows up as
>>>> '[email protected]'
>>>>
>>>> I cannot create a wave in the console and see it in the sandbox, but
>>>> I'm hoping these problems are related.
>>>>
>>>> Any ideas?
>>>>
>>>> I can post the logs if that will help...
>>>> Thanks!
>>>> Ben
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "Wave Protocol" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected].
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/wave-protocol?hl=en.
>>>>
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Wave Protocol" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected].
>>> For more options, visit this group at
>>> http://groups.google.com/group/wave-protocol?hl=en.
>>>
>>>
>>
>>
>>
>> --
>> Benjamin Nortier
>> e: [email protected]
>> c: +44 (0)778 946 1959
>> gtalk: [email protected]
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Wave Protocol" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/wave-protocol?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/wave-protocol?hl=en.
>
>
--
Benjamin Nortier
e: [email protected]
c: +44 (0)778 946 1959
gtalk: [email protected]
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
