🔐 A lightweight high level library for configuring a http client or server based on SSLContext or other properties such as TrustManager, KeyManager or Trusted Certificates to communicate over SSL TLS for one way authentication or two way authentication provided by the SSLFactory. Support for Java, Scala and Kotlin based clients with examples. Available client examples are: Apache HttpClient, OkHttp, Spring RestTemplate, Spring WebFlux WebClient Jetty and Netty, the old and the new JDK HttpClient, the old and the new Jersey Client, Google HttpClient, Unirest, Retrofit, Feign, Methanol, Vertx, Scala client Finagle, Featherbed, Dispatch Reboot, AsyncHttpClient, Sttp, Akka, Requests Scala, Http4s Blaze, Kotlin client Fuel, http4k Kohttp and Ktor. Also gRPC and ElasticSearch examples are included (by Hakky54)


Basic SSLContext-Kickstart repo stats
4 days ago

Hakky54/sslcontext-kickstart is an open source project licensed under Apache License 2.0 which is an OSI approved license.

SSLContext-Kickstart Alternatives

Similar projects and alternatives to SSLContext-Kickstart based on common topics and language

  • GitHub repo Jetty

    Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more

  • GitHub repo TLS Channel

    A Java library that implements a ByteChannel interface over SSLEngine, enabling easy-to-use (socket-like) TLS for Java applications.

  • GitHub repo DSL-JSON

    High performance JVM JSON library

  • GitHub repo wolfssl

    The wolfSSL library is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3!

  • GitHub repo Simple Java Mail

    Simple API, Complex Emails (JavaMail smtp wrapper)

  • GitHub repo Micronaut

    Micronaut Application Framework

  • GitHub repo springdoc-openapi

    Library for OpenAPI 3 with spring-boot

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better SSLContext-Kickstart alternative or higher similarity.


Posts where SSLContext-Kickstart has been mentioned. We have used some of these posts to build our list of alternatives and similar projects.
  • Easily configure SSL/TLS Connection | 2021-05-05
    I wanted to help myself out from the verbosity make my life easier. One library to configure them all! It should be painless to use, easy to test and debug, and fun to set-it-up. The project is available at GitHub - SSLContext-Kickstart
  • Correct way to use maven dependency scope for library maintainers | 2021-03-13
    I also want to provide some context to make this question more clear. I created sslcontext-kickstart which is just a high-level library for configuring ssl for a server or client. The library has additional separate dependencies which the end-user can use to make it more easy to use for their use case. So the core library has only a dependency on slf4j-api. However there are separate libraries which contain mappers which I also created for apache4, apache5, netty and jetty which relay on the core library. Apache4, apache5, netty and jetty are currently a compile scoped dependency and therefor the end-user will also get the version which is specified in my pom. Let's assume someone is using the apache4 version. So should the end-user exclude the dependency manually when they are using my library and don't want the specific transitive apache4 dependency? Or should I mark apache4 as provided scope type. In that way there will be no transitive dependency, however the end-user should have the apache4 dependency present on their classpath or else they will get a runtime exception when they use my library.