Return-Path: Delivered-To: apmail-mina-users-archive@www.apache.org Received: (qmail 91093 invoked from network); 15 Jan 2011 18:19:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jan 2011 18:19:01 -0000 Received: (qmail 57863 invoked by uid 500); 15 Jan 2011 18:19:01 -0000 Delivered-To: apmail-mina-users-archive@mina.apache.org Received: (qmail 57789 invoked by uid 500); 15 Jan 2011 18:19:00 -0000 Mailing-List: contact users-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@mina.apache.org Delivered-To: mailing list users@mina.apache.org Received: (qmail 57781 invoked by uid 99); 15 Jan 2011 18:19:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Jan 2011 18:19:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bernd.fondermann@googlemail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-ew0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Jan 2011 18:18:54 +0000 Received: by ewy22 with SMTP id 22so2283383ewy.2 for ; Sat, 15 Jan 2011 10:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ZOPRBCgcMWt5tdVWOu2MeD8AF5Ulh0shszacIqPXXsU=; b=PfqG74XRi4amq8xpyV7tTxYVGd5Sx8rIYSHMPuY9zyqfHAA1KpA4h4U8Yxgk8NzM+G 0CQnKLm8w+18+dxd280Mxz6dOeTTo1wYGgaxs+oRfTJ5MyK5jvdC1r+OcJN3tY1OvVLm 7WDqUgBOqvO1vzaTQRAL31OuGQnZP0aMHVg2g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=i52GyaQVx62KGVIngn3NWqfSCuPqHOCMbhRdiT1zYS80XtDRmfEfhHSR4Y1Y3o8opT UQJ0OtGXvE6wJkoPwJF8hJayaTb/kNztv+V8XQnowtyfW2n08QMRkPypHjqNdELEhvoD G8JxIvrTEEg6ciuyVG65BfBc6ijEN95ocvAxU= MIME-Version: 1.0 Received: by 10.213.17.17 with SMTP id q17mr868412eba.10.1295115514401; Sat, 15 Jan 2011 10:18:34 -0800 (PST) Received: by 10.213.33.11 with HTTP; Sat, 15 Jan 2011 10:18:34 -0800 (PST) In-Reply-To: References: <3F85BA56-B34A-4738-9F26-77FA8331E945@pre-dev.de> Date: Sat, 15 Jan 2011 19:18:34 +0100 Message-ID: Subject: Re: [VYSPER] automatic account registration From: Bernd Fondermann To: users@mina.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org There is another option in TRUNK (future Vysper 0.7). An Admin can create accounts for new users directly from his client by issueing an administrative command. However, this does not cover new user's creating accounts for themselves. Please note that these accounts are transient in the default deployment, which does not persist accounts. Bernd On Sat, Jan 15, 2011 at 18:07, Niklas Gustavsson wrote: > On Sat, Jan 15, 2011 at 5:06 PM, Peter Frohberg wrote: >> Is it with the "stand-alone" version of VYSPER possible, that users create accounts from their xmpp-client. > > No, this is specified in http://xmpp.org/extensions/xep-0077.html > which Vysper does not currently support. This is certainly a XEP we're > interested in supporting in Vysper. If you don't want to wait for us > to get around to implementing it, feel free to look into working on it > yourself. We're happy to assist where needed. > >> The only way for me to create accounts is currently to define them manually within the spring-configure.xml XML file. > > You can also choose to implement your own AccountManagement against > some other data source or use JCR. > > /niklas >