SSL with Grizzly and Jersey
grizzly, java, jersey, rest, ssl
Solution
IMO you can use different Factory method to initialize secured Grizzly HttpServer:
HttpServer secure = GrizzlyServerFactory.createHttpServer(BASE_URI_SECURED,
ContainerFactory.createContainer(HttpHandler.class, rc),
true,
new SSLEngineConfigurator(sslCon));
If you initialize the server like this, you don't need to stop and reconfigure it again.
Hope this will help.
Problem
I'm trying to get grizzly to use SSL encryption and still work fine with Jersey. I've looked all over the Internet, and I find all kinds of different attempts at SSL with Grizzly and Jersey. Seems like there are different ways of doing it depending on which version you are using, and how you decided to implement it. I haven't been able to get any examples to work with my code yet. Here's how I start up my server: ``` static HttpServer startSecureServer() throws IOException{ ResourceConfig rc=new PackagesResourceConfig("server.grizzlyresources"); SSLContextConfigurator sslCon=new SSLContextConfigurator(); sslCon.setKeyStoreFile(ConfigLoader.getKeystoreLocation()); // contains server keypair sslCon.setKeyStorePass(ConfigLoader.getKeystorePassword()); System.out.println("Starting server on port "+ConfigLoader.getHttpsServerPort()); HttpServer secure=GrizzlyServerFactory.createHttpServer(BASE_URI_SECURED, rc); secure.stop(); HashSet<NetworkListener> lists=new HashSet<NetworkListener>(secure.getListeners()); for (NetworkListener listener : lists){ listener.setSecure(true); SSLEngineConfigurator ssle=new SSLEngineConfigurator(sslCon); listener.setSSLEngineConfig(ssle); secure.addListener(listener); System.out.println(listener); } secure.start(); return secure; } private static URI getBaseURISecured(){ return UriBuilder.fromUri("https://0.0.0.0/").port(ConfigLoader.getHttpsServerPort()).build(); } private static final URI BASE_URI_SECURED = getBaseURISecured(); ``` ConfigLoader loads in information from a config file. When I run this code, it starts up the server, it finds the resources in the server.grizzlyresources package, and it works great! Except for one thing. The server isn't secured. I can telnet into it and send an HTTP request in plain text for one of my resources, and it will return it. So the code works for starting up the server, but the whole SSL part of it is just being bypassed. Any ideas how to fix this or why it might be doing this? Here's the output to the console when I run it: ``` Starting server on port 9999 Jan 13, 2014 9:51:08 AM com.sun.jersey.api.core.PackagesResourceConfig init INFO: Scanning for root resource and provider classes in the packages: server.grizzlyresources Jan 13, 2014 9:51:08 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses INFO: Root resource classes found: class server.grizzlyresources.SessionResource class server.grizzlyresources.LoginResource Jan 13, 2014 9:51:08 AM com.sun.jersey.api.core.ScanningResourceConfig init INFO: No provider classes found. Jan 13, 2014 9:51:08 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate INFO: Initiating Jersey application, version 'Jersey: 1.12 02/15/2012 04:51 PM' Jan 13, 2014 9:51:09 AM org.glassfish.grizzly.http.server.NetworkListener start INFO: Started listener bound to [0.0.0.0:9999] Jan 13, 2014 9:51:09 AM org.glassfish.grizzly.http.server.HttpServer start INFO: [HttpServer] Started. Jan 13, 2014 9:51:09 AM org.glassfish.grizzly.http.server.NetworkListener stop INFO: Stopped listener bound to [0.0.0.0:9999] NetworkListener{name='grizzly', host='0.0.0.0', port=9999, secure=true} Jan 13, 2014 9:51:09 AM org.glassfish.grizzly.http.server.NetworkListener start INFO: Started listener bound to [0.0.0.0:9999] Jan 13, 2014 9:51:09 AM org.glassfish.grizzly.http.server.HttpServer start INFO: [HttpServer] Started. ``` I'm using Grizzly 2.2.1, and Jersey 1.12. Thanks a bunch!