I'k looking for a xmpp windows client with SSO feature in a Windows Domain.
I've tried pandion but it doens't work.
You're likely looking for Kerberos 5 support. The GSSAPI SASL mechanism is how this works on the wire. I think Psi implements GSSAPI. Setting this up on the server side can be hard, so please don't assume that if it doesn't work the first time it is the client's fault.
Spark + Openfire (http://community.igniterealtime.org/docs/DOC-1362)
Related
I am setting up hubot with a slack adapter for an enterprise and would like to know if the socket connection between Hubot and Slack is secure.
If not, how can it be secured?
Its hard to say in general whether a product would be regards as "secure" for your enterprise. It all depends on the security requirements specific to your business. e.g. a defense contractor might have much higher security requirements than a retailer.
To answer your question I would therefore suggest to research the security specifics of this product and then compare them with the security requirements of your enterprise.
Here is an overview about the security architecture to get you started:
Hubot uses Slack's RTM API which uses WebSockets as main
communication protocol
To start a connection you need to call either the rtm.start or
rtm.connect endpoint, which is secured by HTTPS. Both endpoints require you to
provide authentication via a Oauth 2.0 token.
Those endpoint return a custom URL for your WebSocket session
All WebSocket communication uses the secure WSS protocol, which applies TLS to secure the connection
I have raised a ticket with Slack support team and they confirmed that connection is WSS and uses TLS 1.2 which makes it secure for enterprise. Thanks!
I am looking to implement WebSocket communication via ejabberd xmpp server...
The only module that I have found so far is this repository:
ejabberd-websockets
This repository has not been updated for 4 year so I do not feel very comfortable using it.
Any alternatives or reviews on above mentioned repository?
From ejabberd 15.03 version, WebSockets are fully supported, as stated here:
ejabberd 15.03 released, with Websockets support
You could also try node-xmpp-bosh which is a node.js based connection manager that sits in front of the XMPP server and handles BOSH and XMPP over WebSockets. The XMPP server sees all traffic as standard XMPP traffic.
I know that the BOSH part works well, but haven't tried WebSockets.
When I connect to signalR hosted in same virtual directory, I get data via websocket transport. But in case of cross domain, long polling is getting used as a transport.
Here browser compatibility is not an issue as I am trying in Chrome browser.
What I can do to use websocket as a transport in case of cross domain.
I have tried every possible solution available on net, including available at signalR wiki.
https://github.com/SignalR/SignalR/wiki/SignalR-JS-Client-Hubs
Thanks David for answering my question in the comments:
Because only IIS8 supports websockets and neither SSE or ForeverFrame works cross domain so you're stuck with long polling –
I'm looking for a way to host an AJAX web client on my jabber server for people that can't install a real jabber client.
I tried JWchat but it hasn't been updated since 2004 and doesn't work anymore.
Yes there is:
Strophe.js http://strophe.im/strophejs/ is pretty much what most people use currently. You can find the code here: https://github.com/metajack/strophejs
Please consider the following scenario:
VNC Client try to connect with a VNC Server which is behind a NAT.
I have written a port forwarder in java which help me achieving above task, and it works fine.
Now I need to, somehow, add a connection brokering functionality within this forwarder so that I can also intercept the communication between VNC Client – Server, and authenticate the VNC Client within the forwarding utility as well.
You may have guessed that actually I am using the password received from VNC Client for some authentication in my app. As the RFB Server can be implemented at application layer, I guess this interception is possible... VNCAuthentication (DES encryption/decryption) is used in all above communication. Upon successful authentication within the forwarding utility I shall just let the forwarding continue for that respective client, else I can close it (stop forwarding).
I have tried some implementation, also tried customizing a java implementation of rfb server... but still not able to get there. It will take some time, I know, but need to confirm if I am thinking straight.
Please let me know if the implementation of above scenario is ambiguous, not possible, or illegitimate and if this is possible, let me have some guild lines...
This seems like a good implementation. Think of it like a VNC proxy, just like an HTTP(S) proxy. There are also HTTP authenticating proxies. You're implementing part of the VNC protocol to create an authenticating VNC proxy.
Maybe you can get some inspiration from VNCProxy, an existing Java VNC proxy.