* Jonas Wielicki <[email protected]> [2018-01-25 10:26]: > Version 0.1.0 of XEP-0401 (Easy User Onboarding) has been released. > > This document defines a protocol and URI scheme for user invitation in > order to allow a third party to register on a server. The goal of this > is to make onboarding for XMPP IM newcomers as easy as possible.
This is a good moment to pick up Council feedback and to ignite discussion. Both Dave and Kev addressed the existence of Data Forms (XEP-0004) in the IBR flow, and wondered why it isn't used in this context. The typical IBR flow (XEP-0077, ยง3.1) is as follows: 1. client requests a form: IQ/<query xmlns='jabber:iq:register'/> 2. server returns either: - mandatory element list (username, password, email) - flexible registration data form 3. client fills in fields, sends response The problem was that we need to signal to the server in step 1 that we have a `preauth` token to share. In retrospect I realize that we can also use the <preauth xmlns='urn:xmpp:invite:0'/> payload in the IQ-get and let the server return us a Data Form. However, then we need to define how the client can determine whether this Data Form is a PREAUTH compatible form, and whether the user is still required to add more content. In that specific case, Forms are too flexible for what we need, and I'd like to stick to the one-more-element registration query. Comments / suggestions please! Georg -- || http://op-co.de ++ GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N ++ || gpg: 0x962FD2DE || o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+ || || Ge0rG: euIRCnet || X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y? || ++ IRCnet OFTC OPN ||_________________________________________________||
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
