Wish I could answer yes. I've been struggling with WSS for 2 days now.
Using WS in dev mode directly to play on port 9000 works great. I have it working from the browser and even from a java lib from android, on my local lan.
But when I try against my production SSL server I am having strange problems. I am not using the built in SSL in Play, instead I am using Play only in clear text on port 9000 and use Nginx 1.6.0 as a reverse proxy in front of Play, Nginx is running on both port 80 and 443.
I've added the needed nginx configs to proxy the websocket but I still get strange results. For instance, when I connect to WSS on port 443 using a self-signed cert (already trusted by the browser and OS) Things seem to connect and run fine, but I can't disconnect. Called either websocket.close() in the browser does nothing. The connection stays active, weird. And calling websocket.close() from the Play server seems to leave the connection open on the browser side as well. I think maybe its only closing half of the websocket on the other side of the proxy? Not sure exactly.
I think using WSS with SSLContext from Android is another issue entirely. I get a timeout when attempting to connect.
Error creating socket: java.util.concurrent.TimeoutException: No response received after 60000
I think this is due to the self-signed cert and maybe this websocket lib not working correctly with custom SSLContext. I'm using, async-http-client. There are others out there I still need to try. Does anyone know of a websocket client I can use from Android with support for custom SSLContext with client authentication support?
But, the Android client works fine over unecrypted WS.
...still looking for my own answers.
-Tony