github
/
acme4j
mirror of https://github.com/shred/acme4j
1
0
Fork 0
Code Issues Releases Wiki Activity
299 Commits
4 Branches
43 Tags
3.9 MiB
Java 99.3%
Python 0.5%
Shell 0.2%
 
 
 
Go to file
Richard Körber 22ed05de8e
Remove GitHub ribbon 
It links to an external image and thus is not GDPR compliant.
 		2018-05-21 10:03:12 +02:00
.github Add issue template and contribution rules 2018-01-07 14:21:46 +01:00
acme4j-client Remove deprecated code 2018-03-17 13:30:34 +01:00
acme4j-example [maven-release-plugin] prepare for next development iteration 2018-03-13 23:21:32 +01:00
acme4j-utils Remove deprecated code 2018-03-17 13:30:34 +01:00
src/site Remove GitHub ribbon 2018-05-21 10:03:12 +02:00
.gitignore Initial commit 2015-12-04 21:28:12 +01:00
.gitlab-ci.yml Gitlab CI: Use jacoco and sonar 2016-12-16 00:38:37 +01:00
.project Project start 2015-12-09 01:24:03 +01:00
CONTRIBUTING.md Add issue template and contribution rules 2018-01-07 14:21:46 +01:00
LICENSE-APL.txt Initial commit 2015-12-04 21:28:12 +01:00
README.md Remove local certificate after it has been revoked by LE 2018-03-17 12:36:51 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2018-03-13 23:21:32 +01:00

README.md

ACME Java Client build status

This is a Java client for the Automatic Certificate Management Environment (ACME) protocol.

ACME is a protocol that a certificate authority (CA) and an applicant can use to automate the process of verification and certificate issuance.

This Java client helps connecting to an ACME server, and performing all necessary steps to manage certificates.

It is an independent open source implementation that is not affiliated with or endorsed by Let's Encrypt.

ACME v1

This acme4j branch implements the deprecated ACME v1 protocol. It should only be used for existing code, and for connecting to CAs that do not provide an ACME v2 service.

For new projects, it is recommended to use acme4j version 2, which fully implements the current ACME v2 protocol.

Existing code should be migrated to acme4j version 2 (see the migration guide). Let's Encrypt has not yet announced a sunset date for ACME v1, so there seems to be plenty of time for migration at the moment.

This acme4j v1 branch is not actively maintained any more. It will only get bugfixes and security updates, but no new features. As soon as Let's Encrypt officially ends its ACME v1 support, work on this branch will be stopped.

Features

  • Supports the "ACME v1" protocol that is used by Let's Encrypt
  • Easy to use Java API
  • Requires JRE 8u101 or higher
  • Built with maven, packages available at Maven Central
  • Small: acme4j-client only requires jose4j and slf4j as dependencies
  • Only the optional acme4j-utils module requires Bouncy Castle
  • Extensive unit tests

Usage

Contribute

  • Fork the Source code at GitHub. Feel free to send pull requests. However, work on this branch is discontinued in favor of the ACMEv2 implementation in the master branch. We will only accept bug fixes and security related patches.
  • Found a bug? File a bug report. Please add a note that you are referring to the old ACMEv1 implementation!

License

acme4j is open source software. The source code is distributed under the terms of Apache License 2.0.

Acknowledgements

  • I would like to thank Brian Campbell and all the other jose4j developers. acme4j would not exist without your excellent work.
  • I also like to thank everyone who contributed to acme4j.