You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[COSE RS1](https://www.rfc-editor.org/rfc/rfc8812.html#section-2) as a supported algorithm with ACME `device-attest-01` challenge (smallstep/certificates#1663)
98
+
99
+
### Changed
100
+
101
+
- In an RA setup, let the CA decide the RA certificate lifetime (smallstep/certificates#1764)
102
+
- Use Debian Bookworm in Docker containers (smallstep/certificates#1615)
103
+
- Error message for CSR validation (smallstep/certificates#1665)
104
+
- Updated dependencies
105
+
106
+
### Fixed
107
+
108
+
- Stop CA when any of the required servers fails to start (smallstep/certificates#1751). Before the fix, the CA would continue running and only log the server failure when stopped.
109
+
- Configuration loading errors when not using context were not returned. Fixed in [cli-utils/109](https://github.com/smallstep/cli-utils/pull/109).
110
+
- HTTP_PROXY and HTTPS_PROXY support for ACME validation client (smallstep/certificates#1658).
111
+
112
+
### Security
113
+
114
+
- Upgrade to using cosign v2 for signing artifacts
115
+
28
116
## [0.25.1] - 2023-11-28
29
117
30
118
### Added
@@ -36,7 +124,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
36
124
37
125
- Generation of first provisioner name on `step ca init` in (smallstep/certificates#1566)
38
126
- Processing of SCEP Get PKIOperation requests in (smallstep/certificates#1570)
39
-
- Support for signing identity certificate during SSH sign by skipping URI validation in (smallstep/certificates#1572)
127
+
- Support for signing identity certificate during SSH sign by skipping URI validation in (smallstep/certificates#1572)
40
128
- Dependency on `micromdm/scep` and `go.mozilla.org/pkcs7` to use Smallstep forks in (smallstep/certificates#1600)
41
129
- Make the Common Name validator for JWK provisioners accept values from SANs too in (smallstep/certificates#1609)
Copy file name to clipboardExpand all lines: README.md
+42-30Lines changed: 42 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,49 +1,62 @@
1
-
# Step Certificates
1
+
# step-ca
2
2
3
-
`step-ca` is an online certificate authority for secure, automated certificate management. It's the server counterpart to the [`step` CLI tool](https://github.com/smallstep/cli).
- Issue X.509 certificates for your internal infrastructure:
7
-
- HTTPS certificates that [work in browsers](https://smallstep.com/blog/step-v0-8-6-valid-HTTPS-certificates-for-dev-pre-prod.html) ([RFC5280](https://tools.ietf.org/html/rfc5280) and [CA/Browser Forum](https://cabforum.org/baseline-requirements-documents/) compliance)
8
-
- TLS certificates for VMs, containers, APIs, mobile clients, database connections, printers, wifi networks, toaster ovens...
9
-
- Client certificates to [enable mutual TLS (mTLS)](https://smallstep.com/hello-mtls) in your infra. mTLS is an optional feature in TLS where both client and server authenticate each other. Why add the complexity of a VPN when you can safely use mTLS over the public internet?
9
+
`step-ca` is an online certificate authority for secure, automated certificate management for DevOps.
10
+
It's the server counterpart to the [`step` CLI tool](https://github.com/smallstep/cli) for working with certificates and keys.
11
+
Both projects are maintained by [Smallstep Labs](https://smallstep.com).
12
+
13
+
You can use `step-ca` to:
14
+
- Issue HTTPS server and client certificates that [work in browsers](https://smallstep.com/blog/step-v0-8-6-valid-HTTPS-certificates-for-dev-pre-prod.html) ([RFC5280](https://tools.ietf.org/html/rfc5280) and [CA/Browser Forum](https://cabforum.org/baseline-requirements-documents/) compliance)
- For people, in exchange for single sign-on ID tokens
17
+
- For people, in exchange for single sign-on identity tokens
12
18
- For hosts, in exchange for cloud instance identity documents
13
19
- Easily automate certificate management:
14
-
- It's an ACME v2 server
15
-
- It has a JSON API
20
+
- It's an [ACME server](https://smallstep.com/docs/step-ca/acme-basics/) that supports all [popular ACME challenge types](https://smallstep.com/docs/step-ca/acme-basics/#acme-challenge-types)
16
21
- It comes with a [Go wrapper](./examples#user-content-basic-client-usage)
17
22
- ... and there's a [command-line client](https://github.com/smallstep/cli) you can use in scripts!
18
23
19
-
Whatever your use case, `step-ca` is easy to use and hard to misuse, thanks to [safe, sane defaults](https://smallstep.com/docs/step-ca/certificate-authority-server-production#sane-cryptographic-defaults).
20
-
21
24
---
22
25
23
-
**Don't want to run your own CA?**
24
-
To get up and running quickly, or as an alternative to running your own `step-ca` server, consider creating a [free hosted smallstep Certificate Manager authority](https://info.smallstep.com/certificate-manager-early-access-mvp/).
26
+
### Comparison with Smallstep's commercial product
27
+
28
+
`step-ca` is optimized for a two-tier PKI serving common DevOps use cases.
29
+
30
+
As you design your PKI, if you need any of the following, [consider our commerical CA](http://smallstep.com):
31
+
- Multiple certificate authorities
32
+
- Active revocation (CRL, OSCP)
33
+
- Turnkey high-volume, high availability CA
34
+
- An API for seamless IaC management of your PKI
35
+
- Integrated support for SCEP & NDES, for migrating from legacy Active Directory Certificate Services deployments
36
+
- Device identity — cross-platform device inventory and attestation using Secure Enclave & TPM 2.0
@@ -52,7 +65,6 @@ Setting up a *public key infrastructure* (PKI) is out of reach for many small te
52
65
53
66
- Choose key types (RSA, ECDSA, EdDSA) and lifetimes to suit your needs
54
67
-[Short-lived certificates](https://smallstep.com/blog/passive-revocation.html) with automated enrollment, renewal, and passive revocation
55
-
- Capable of high availability (HA) deployment using [root federation](https://smallstep.com/blog/step-v0.8.3-federation-root-rotation.html) and/or multiple intermediaries
56
68
- Can operate as [an online intermediate CA for an existing root CA](https://smallstep.com/docs/tutorials/intermediate-ca-new-ca)
57
69
-[Badger, BoltDB, Postgres, and MySQL database backends](https://smallstep.com/docs/step-ca/configuration#databases)
58
70
@@ -127,5 +139,5 @@ and visiting http://localhost:8080.
127
139
128
140
## Feedback?
129
141
130
-
* Tell us what you like and don't like about managing your PKI - we're eager to help solve problems in this space.
131
-
* Tell us about a feature you'd like to see! [Add a feature request Issue](https://github.com/smallstep/certificates/issues/new?assignees=&labels=enhancement%2C+needs+triage&template=enhancement.md&title=), [ask on Discussions](https://github.com/smallstep/certificates/discussions), or hit us up on [Twitter](https://twitter.com/smallsteplabs).
142
+
* Tell us what you like and don't like about managing your PKI - we're eager to help solve problems in this space.[Join our Discord](https://u.step.sm/discord) or [GitHub Discussions](https://github.com/smallstep/certificates/discussions)
143
+
* Tell us about a feature you'd like to see! [Request a Feature](https://github.com/smallstep/certificates/issues/new?assignees=&labels=enhancement%2C+needs+triage&template=enhancement.md&title=)
0 commit comments