[3878] in BarnOwl Developers
Re: barnowl and xmpp
daemon@ATHENA.MIT.EDU (Ken Kokubo)
Fri Nov 13 14:02:33 2015
To: barnowl-dev@mit.edu
From: Ken Kokubo <kokubo@mit.edu>
Date: Fri, 13 Nov 2015 14:02:56 -0500
In-Reply-To: <5629431A.1070301@mit.edu>
This is a multi-part message in MIME format.
--------------000303030400040405000206
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Hi Adam and all,
Sorry for the delay. Just to follow up, here is the response to the
question you asked.
The MIT community is looking for broader features and functionality
since the deployment of Openfire. The Openfire platform continues to be
a good text based IM platform, but it has failed to add the enhanced
features to keep pace with the expectations and requirements of our user
community. These requirements include integration with our calendar
systems, voice/video systems, WebEx collaboration systems, while
providing support for the current XMPP clients. This has forced us to
take a step back and re-assess our SSO requirements in light of the
changing landscape, and while we continue to strive to provide a
seamless SSO experience, we also must balance that need with the
requirements for new features and functionality. While the new solution
does not provide SSO, it does provide LDAP BIND functionality for
Kerberos credentials.
Thanks,
Ken
On 10/22/15 4:12 PM, Ken Kokubo wrote:
> Hi Adam,
>
> That I do not know, but can find out.
>
> On 10/22/15 4:11 PM, Adam Glasgall wrote:
>> On Thu, Oct 22, 2015 at 03:42:34PM -0400, Ken Kokubo wrote:
>>> Hello,
>>>
>>> I was wondering how active this list is and possibly looking for
>>> some assistance.
>>>
>>> We (at IS&T) will be retiring the current Openfire XMPP server soon
>>> (jabber.mit.edu). Our existing Cisco Unified Communications Manager
>>> cluster includes an XMPP server and we will be migrating the service
>>> there. It can be accessed as a standalone server, or with a Cisco
>>> client that integrates messaging with SIP
>>> softphone/voicemail/videoconferencing and some webex integration.
>>>
>>> We have tested Pidgin, Adium, Messages and it has been asked if
>>> Barnowl could work. One of the key issues being the new service
>>> can't handle SSO.
>>>
>> The support for Kerberos SSO was one of the main factors in selecting
>> the original XMPP server deployment at MIT; what has changed to make
>> that factor no longer important?
>>
>> Thanks,
>>
>> Adam
>>> Just wondering if anyone would be interested in taking a look.
>>>
>>>
>>> Thanks,
>>> Ken
>
--
Ken Kokubo
SDI Network Engineer
IS&T Collaboration Platform
W92 114G
617-324-4646
--------------000303030400040405000206
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Adam and all,<br>
<br>
Sorry for the delay. Just to follow up, here is the response to the
question you asked.<br>
<br>
<font face="Calibri,sans-serif">The MIT community is looking for
broader features and functionality since the deployment of
Openfire. The Openfire platform continues to be a good text based
IM platform, but it has failed to add the enhanced features to
keep pace with the expectations and requirements of our user
community. These requirements include integration with our
calendar systems, voice/video systems, WebEx collaboration
systems, while providing support for the current XMPP clients.
This has forced us to take a step back and re-assess our SSO
requirements in light of the changing landscape, and while we
continue to strive to provide a seamless SSO experience, we also
must balance that need with the requirements for new features and
functionality. While the new solution does not provide SSO, it
does provide LDAP BIND functionality for Kerberos credentials.<br>
<br>
<br>
Thanks,<br>
Ken<br>
</font><br>
<div class="moz-cite-prefix">On 10/22/15 4:12 PM, Ken Kokubo wrote:<br>
</div>
<blockquote cite="mid:5629431A.1070301@mit.edu" type="cite">Hi Adam,
<br>
<br>
That I do not know, but can find out.
<br>
<br>
On 10/22/15 4:11 PM, Adam Glasgall wrote:
<br>
<blockquote type="cite">On Thu, Oct 22, 2015 at 03:42:34PM -0400,
Ken Kokubo wrote:
<br>
<blockquote type="cite">Hello,
<br>
<br>
I was wondering how active this list is and possibly looking
for
<br>
some assistance.
<br>
<br>
We (at IS&T) will be retiring the current Openfire XMPP
server soon
<br>
(jabber.mit.edu). Our existing Cisco Unified Communications
Manager
<br>
cluster includes an XMPP server and we will be migrating the
service
<br>
there. It can be accessed as a standalone server, or with a
Cisco
<br>
client that integrates messaging with SIP
<br>
softphone/voicemail/videoconferencing and some webex
integration.
<br>
<br>
We have tested Pidgin, Adium, Messages and it has been asked
if
<br>
Barnowl could work. One of the key issues being the new
service
<br>
can't handle SSO.
<br>
<br>
</blockquote>
The support for Kerberos SSO was one of the main factors in
selecting
<br>
the original XMPP server deployment at MIT; what has changed to
make
<br>
that factor no longer important?
<br>
<br>
Thanks,
<br>
<br>
Adam
<br>
<blockquote type="cite">Just wondering if anyone would be
interested in taking a look.
<br>
<br>
<br>
Thanks,
<br>
Ken
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ken Kokubo
SDI Network Engineer
IS&T Collaboration Platform
W92 114G
617-324-4646</pre>
</body>
</html>
--------------000303030400040405000206--
