Commit Graph

14 Commits

Author SHA1 Message Date
peterbakker
32b9d432db naming changes
readme update
2020-04-28 20:38:51 +02:00
Michael Munger
713285f8b5 Add support to get certificate chain as separate certificates
- https://github.com/afosto/yaac/issues/10
- The purpose is to support web servers such as apache < 2.4.8
  where the intermediate certificate needs to be separate
- Add method Helper::splitCertificate to parse cert chain
- Add param to Certificate::getCertificate($asChain = true)
  to maintain bc and get the certificate with or without chain
- Add method Certificate::getIntermediateCertificate to get just
  the intermediate certificate
2020-04-24 16:36:49 -06:00
Michael Munger
e654975374 Remove unused use statements from helper 2020-04-24 16:32:07 -06:00
peterbakker
fae8ff885c Only sleep if there is work to do 2020-03-19 20:01:45 +01:00
peterbakker
6455a33db1 changed backoff factor for DNS validation 2020-03-19 19:41:20 +01:00
peterbakker
98d07ff83c added dns support 2020-03-18 21:05:04 +01:00
peterbakker
505ce369e5 Merge branch 'lordelph-master'
# Conflicts:
#	src/Data/Authorization.php
2020-03-18 19:57:43 +01:00
peterbakker
b7ff268e4e Improved http validation with exponential backoff
Added documentation
Simplified HTTP validation flow (no longer need challenge to get file contents)
Updated README.md
2020-03-18 19:31:57 +01:00
Paul Dixon
eec278cdd1 fix erroneous loop and status check (also suggested by mgilfillan) 2020-03-17 18:28:42 +00:00
Paul Dixon
c2532e0dab add support for DNS validation
- new constant Client::VALIDATION_DNS
- added Authorization::getDnsChallenge to get the challenge
- added Authorization::getTxtRecord to get the TXT record value
- added Helper::waitForDNS to provide an easy way to wait for changes
- updated documentation to illustrate DNS validation
2020-03-17 18:27:27 +00:00
Mike Gilfillan
6b55f256ae Fix incorrect comparison when auto-retrying authorization
Previously only 1 attempt to authorize would be made
2020-03-03 15:56:42 +00:00
Mike Gilfillan
f1d31dee88 Check the authorization status is "valid" rather than "ready"
According to https://tools.ietf.org/html/rfc8555#section-7.1.4 the
status of an authorization object can only be "pending", "valid", or
"revoked".

An order can have a status of "ready" but never an authorization.
2020-03-03 15:45:02 +00:00
peterbakker
4c7b6b8e60 Updated the namespace to Acme 2020-02-13 09:04:16 +01:00
peterbakker
5a35b6af35 Initial commit 2020-02-13 08:55:12 +01:00