mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bf_...@brainlounge.de>
Subject Re: Vysper AccountManagement - what if i need other data other than username and pw
Date Sat, 05 Sep 2009 11:29:57 GMT
Hi Ely,

thanks for following up. I think I still don't totally understand what
you want to do. Next try...

Ely Celino wrote:
> Well, it would be nice if we could have something like
> myXmppServer.addDomain("anotherdomain.com"). 

Sure, but this would require substantial refactorings.

> But, if it would mess things up
> I would just put out registration out of xmpp protocol. 

If you use a plain vanilla vysper from SVN, there is no possibility of
account registration of users yet using the XMPP protocol. Neither
in-band registration (XEP-0077) nor using service administration
(XEP-0133, XEP-0050). AccountManagement is only accessible within the
JVM, not via XMPP.

> Then, I would sign
> in account using username@mydomain.com/clientid. 

Why would you do that? What does that help? XMPP only assigns resources
(what you depict as "/clientid" here) _after_ authentication.

Are you talking here about your own heavily customized version of Vysper?

> I believe it is possible to
> specify the resource to be used upon authentication.

+ Resource registration is only possible after authentication
+ Accepting the resource id from the client is OPTIONAL for the server
+ Vysper does not accept a client's resource id.

I'm not completely understanding your goal yet, I guess.


> On Sat, Sep 5, 2009 at 2:25 PM, Bernd Fondermann <bf_jak@brainlounge.de>wrote:
>> Fernando Padilla wrote:
>>> username is JID.
>>> JID is name@domain
>>> you don't want to embed the clientid on the domain?
>>> username@clientid.domain
>>> so as long as vysper will recognize all of the sub-domains properly
>> it wouldn't, as far as I can tell.
>>> (anyone want to comment on having vysper server deal with many
>>> sub-domains? or virtual hosts?)
>> you would need to have more than one ServerRuntimeContext (SRC), each
>> serving one domain and write a clever MINABasedSessionContext which is
>> able to route to the right SRC.
>> Having one SRC for more than one Domain requires significant
>> refactorings (hint: SRC.getServerEntity())
>> Patches, as always, are welcome.
>>  Bernd
>>> On 9/3/09 11:58 PM, Ely Celino wrote:
>>>> Hi everyone,
>>>> After implementing AccountManagement, I realized I need other data other
>>>> than user and password in addUser(user, password) function.
>>>> My user db consolidates all my client's record. To distinguish every
>>>> client
>>>> I added client_id column. So if query for a user, I will search by
>>>> username
>>>> plus client_id.
>>>> Of course I could use the username parameter to the addUser function by
>>>> concataning other information to it but we know it will be ugly.
>>>> Is this a limitation of the AccountManagement?

View raw message