> -----Original Message----- > From: [email protected] [mailto:standards- > [email protected]] On Behalf Of Matthew Wild > Sent: Friday, September 21, 2012 11:17 AM > To: XMPP Standards > Subject: Re: [Standards] Question regarding XEP-0077 (In-Band Registration) > > Hi Todd, > > On 20 September 2012 15:53, Todd Herman <[email protected]> wrote: > > I wanted to confirm something in section 3.1.1 of XEP-0077. It seems > > to suggest that you can register with a server prior to > > authentication, meaning that no account is required. We are > > attempting to do this, using OpenFire, right after TLS but before > > SASL. The appropriate Iq is sent and we get the correct response. > > However, when we send the next Iq with the username and password, we > > get back a Failure element with “Not-Authorized”. I wanted to be sure > > that I am understanding section 3.1.1 correctly before I pursue other > options. > > Which iq do you send and which response do you get? Could you perhaps > paste an example XML log? > > Is in-band registration definitely enabled on the server?
I apologize for not responding sooner but the issue is now resolved. It was an issue with SASL still happening do to an asynchronous operation running in the background. I think we may have an additional question as we have a new discrepancy but we are conducting some additional testing before bringing it up. I might be able to head off some questions by asking everyone what they think the term "service", referenced in the XEP is referring too. The XEP lays out two distinct uses for in-band registration: a service registering (I assume on behalf of another user) and the user registering themselves during the negotiation process with a server. We have handled the second case and are working on the first. We assumed that "service" referred to some application (client or component) that already has an account and would simply use the registration process to register another use. Is this an accurate assumption? Thanks for the response. > Regards, > Matthew
