Skip to content
SSL configuration logic, extracted from Play's WS (for use in Akka et al).
Branch: master
Clone or download
raboof Merge pull request #187 from lightbend/mima2.13
Run MiMa on 2.13 artifacts as well
Latest commit ac83e44 Jul 10, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
documentation/src/main/paradox Make validation failures actually fail the build Jul 10, 2019
ssl-config-core/src Restore binary compatibility with 0.3.7 Apr 4, 2019
.gitignore Initial WIP commit, does not compile yet Sep 4, 2015
.java-version removed the use of JodaTime from lib (keep in tests) Dec 18, 2015
.travis.yml Merge branch 'master' into scala2.13.0 Jun 10, 2019
build.sbt Run MiMa on 2.13 artifacts as well Jul 10, 2019
version.sbt Updates to 0.4.0 (#148) Apr 4, 2019

SSL Config

Build Status Maven metadata URL

Goal and purpose of this library is to make Play WS library as well as Akka HTTP "secure by default". Sadly, while Java's security has been steadily improving some settings are still left up to the user, and certain algorithms which should never be used in a serious production system are still accepted by the default settings of the SSL/TLS infrastructure. These things are possible to fix, by providing specialized implementations and/or defining additional settings for the Java runtime to use – this is exactly the purpose of SSL Config.

Additional modules offer integration with Play WS (which by default utilises Async Http Client), Akka Http and any other library which may need support from this library.


The project is maintained on two branches:

  • master which requires Java 8 and is used by Akka 2.5.x and later.
  • release-0.1 which is Java 6 compatible (does lots of manual improvements and checks that JDK6 didn't). Currently only the legacy version of Akka Streams & Http (which is 2.0.x) uses this version.

State of this project

ssl-config at this point in time is used primarily internally in Akka HTTP, and is being evolved towards being "the place" one configures all possible SSL/TLS related settings, mostly focused on the client side of things.

The project is hosted externally of either Akka or Play, in order to foster convergence and re-use of the more tricky bits of configuring TLS.

Binary compatibility is not guaranteed between versions (in the 0.x.z series) of ssl-config at this point in time. We aim to stabilise the APIs and provide a stable release eventually.


Docs are available on:

Recommended reading

An excellent series by Will Sargent about making Play WS (from which this library originates) "secure by default":


Run script and turn the tag into a Release in GitHub to make sure notifications are sent out.


Lightbend 2015-2019, Apache 2.0

You can’t perform that action at this time.