The Wayback Machine - https://web.archive.org/web/20220512151055/https://github.com/topics/certificate-authority
Skip to content
#

certificate-authority

Here are 278 public repositories matching this topic...

certificates
tashian
tashian commented Jan 10, 2022

The recommendation is to set Cache-Control: private, no-store on any endpoint with sensitive information. Because while you can protect the traffic with TLS, you also need to keep sensitive information out of a client's (unencrypted) HTTP cache. I'm not sure how relevant this is to the API context of step-ca though—I've never seen an HTTP client library that caches content. But I guess the poi

mutual-tls-ssl

🔐 Tutorial of setting up Security for your API with one way authentication with TLS/SSL and mutual authentication for a java based web server and a client with both Spring Boot. Different clients are provided such as 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 other server examples are available such as jersey with grizzly. Also gRPC, WebSocket and ElasticSearch examples are included

  • Updated Apr 3, 2022
  • Java
pric

Improve this page

Add a description, image, and links to the certificate-authority topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the certificate-authority topic, visit your repo's landing page and select "manage topics."

Learn more