Example of authentication and ColdFusion 10 WebSockets (2)

So last week I wrote a blog entry talking about how to add authentication to an application using WebSockets under ColdFusion 10. I discussed how there were two main ways of doing it. The previous entry discussed onWSAuthenticate, where authentication is done via JavaScript after the client has already viewed the page. In this entry I’ll discuss the second mode, called “Single Sign On” mode. Single Sign On mode, or SSO for short, is basically a way to have your websocket code recognize an already existing login. However, this does not work with just any regular session-based login. You must make use of cflogin. I have to admit that it has been a little while since I used this feature in ColdFusion. Luckily though once you make use of it, it “just works”, which is always a good thing.

Let’s begin with my Application.cfc file. In order for cflogin-based authentication to work, I must make use of the tags within my onRequestStart method and handle both a login attempt and forcing the user to a login page if they are not authenticated.

Note that our authentication here is rather trivial. If you pass in a username of admin or bob, you’re kosher. If you pass in admin, we also set your roles to admin. I’m not going to bother sharing the code for login.cfm, it will be part of the zip attached to the entry, but all it has is a simple form.

Now - once you login - you can run the main index.cfm. This script has a basic WebCocket ‘chat’ setup where you select a category of messages you want to receive and then start messaging. Unlike the previous demo, I am not running the authenticate API as I’m already logged in, or should be.

While there is nothing here specific to security, ColdFusion is aware of your authentication. In fact, check out the message handler CFC I’m using for my WebSocket.

Notice that I’m checking the authenticated key of the subscriberInfo data. This is similar to my last blog entry. You will also notice that I’m logging the data so I can see what is being passed. Here is what gets logged when I first subscribe:

allowSubscribe: {““connectioninfo””:{““connectiontime””:”“June, 08 2012 10:25:21””, ““roles””:”“admin””, ““clientid”“:2137173390, ““authenticated”“:true, ““username””:”“admin””},”“channelname””:”“news””}

Note that my username and roles were both picked up by the WebSocket. I could use this when generating and handling messages. For example, I could broadcast out messages that only get sent to people in the admin role.

Finally - in case you’re curious - when you run wsGetSubscribers on the server side you can also see the same information.

If you would like to demo this, just hit the link below. As I said earlier, you must login with either ‘admin’ or ‘bob’. You can also download the full source code below.

<p>Download attached file.</p>

Raymond Camden's Picture

About Raymond Camden

Raymond is a developer advocate for Extend by Auth0. He focuses on serverless and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support.

Lafayette, LA https://www.raymondcamden.com