Re: A Jabber server over an ASP.NET MVC app with SQL Server and authenticating against an WebService

"Hund, Johannes" <[email protected]>
Newsgroups gmane.network.jabber.devel
Message-ID <C271054E16F8474D9104E1146C767BF12E0F41@DEFTHW99EK1MSX.ww902.siemens.net>
Hi Juan,

Indeed this is a point that I would love to see standardized in some way.
So far, we know that Openfire has a plugin that exposes a webservice (~RESTful-ish) to create/retrieve/update/delete the user accounts on the server.
Also, I would be very surprised if there would not be a module for Prosody, but I am not aware of one.

Both and I guess most of the other servers can deal with LDAP servers if that is an option.

Best Regards
Johannes

-----Ursprüngliche Nachricht-----
Von: JDev [mailto:[email protected]] Im Auftrag von Juan Jose Huelga
Gesendet: Dienstag, 23. September 2014 00:07
An: [email protected]
Betreff: [jdev] A Jabber server over an ASP.NET MVC app with SQL Server and authenticating against an WebService

Hello jdev

I need to setup a chat message service over a working ASP.NET MVC portal that runs with SQL Server as DB backend. User authentication should be against a custom WebService instead of user and passwords stored on a DB. Everything is running on Windows Server.

I have heard about some XMPP implementations like Openfire, Tigasel, Prosody or ejabberd but I haven't used any. My headache is about registration/authentication and roster management through an available API.

Have any of you any idea about my requirements?

Greetings
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected] _______________________________________________
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.