The information for setting up akka-http ssl is very cluttered / inaccurate / dated / and referencing mismatched links from other systems (such as Play WS ssl client configurations) which doesn't really tell you how to implement server-side ssl. Every code example I see out there on how to setup ssl with Akka-http doesn't use the "config-based" setup but does the setup in the code. Those examples are actually missing the critical last piece of initializing the sslContext with the keyManagers, truestManagers, and SecureRandom settings to make it run. (Since the
sslContext was never initialized it throws an initialization error)
sslContext.init(keyManagerFactory.getKeyManagers, tmf.getTrustManagers, SecureRandom.getInstanceStrong)
So putting this together I'm drawling the conclusion:
- the config-based approach to enabling ssl is not completely wired into a functional solution for akka-http
- the examples on the website need to be updated to show a true working setup (see above code snipped that needs to be included to make that happen)
- documentation should be added to not send users down a wild goose chase of trying to implement a config based https setup with Play's WS ssl-config.ssl (at least not until this is offically supported by akka-http)
Am I right with my assumptions or am I missing something here.
Also, is there a timeline on when a true config-based ssl will be functionally complete for akka-http?