🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Carl Tashian 067f9c9a5f
Merge pull request #1252 from smallstep/carl/startup-noconfig-msg
1 day ago
.github Add step-kms-plugin to docker images and build a CGO based one 6 days ago
acme Remove `charset=utf-8` from ACME certificate requests 3 months ago
api Refactor tests stylistically 3 months ago
authority Move to commands/app.go 1 day ago
autocert Use REAMDE.md suggested in code review. 4 years ago
ca successful isEnabled check should not return error 3 weeks ago
cas Fix and/or ignore linting issues 1 month ago
cmd/step-ca Remove deprecated binaries 1 week ago
commands Merge pull request #1252 from smallstep/carl/startup-noconfig-msg 1 day ago
db Add support for renew when using stepcas 3 months ago
debian [action] debian rules syntax 2 years ago
docker Add step-kms-plugin to docker images and build a CGO based one 6 days ago
errs Fix err assert linter warnings - upgrade outdated package 4 months ago
examples Added some example ansible configs (#813) 1 year ago
logging Fix linter warning 6 months ago
monitoring Upgrade newrelic to v3 6 months ago
pki Add provisioner and super admin subject output to `ca init` 3 months ago
policy Render proper policy and constrains errors 4 months ago
scep Provisioner webhooks (#1001) 4 months ago
scripts We now have an armv5 step-ca build; remove guard clause from RA install script 10 months ago
server Address gosec warnings 6 months ago
systemd Fixes #757 1 year ago
templates Ignore principals validations with OIDC 2 months ago
webhook Provisioner webhooks (#1001) 4 months ago
.VERSION Added version operability for `git archive` tarball (non git repo) 4 years ago
.dockerignore Remove dockerignore files that are in the repo. 2 years ago
.gitattributes Added version operability for `git archive` tarball (non git repo) 4 years ago
.gitignore Add go workspaces files to gitignore 5 months ago
.gitleaksignore [actiono] Update workflows 4 months ago
.goreleaser.yml Add scoop back to goreleaser 2 days ago
.version.sh Use sh instead of bash in .version.sh script 4 months ago
CHANGELOG.md Remove deprecated binaries 1 week ago
CONTRIBUTING.md Remove deprecated docs directory 3 months ago
LICENSE Add full version of the license. 3 years ago
Makefile Remove deprecated binaries 1 week ago
README.md Update build status svg and link to github actions 5 months ago
SECURITY.md Create SECURITY.md 6 months ago
cosign.pub [action] use cosign to sign over goreleaser artifacts 1 year ago
go.mod Merge pull request #1245 from smallstep/dependabot/go_modules/go.step.sm/crypto-0.23.2 3 days ago
go.sum Merge pull request #1245 from smallstep/dependabot/go_modules/go.step.sm/crypto-0.23.2 3 days ago
icon.png Commit icons. 4 years ago
icon.svg Commit icons. 4 years ago

README.md

Step Certificates

step-ca is an online certificate authority for secure, automated certificate management. It's the server counterpart to the step CLI tool.

You can use it to:

  • Issue X.509 certificates for your internal infrastructure:
    • HTTPS certificates that work in browsers (RFC5280 and CA/Browser Forum compliance)
    • TLS certificates for VMs, containers, APIs, mobile clients, database connections, printers, wifi networks, toaster ovens...
    • Client certificates to enable mutual TLS (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?
  • Issue SSH certificates:
    • For people, in exchange for single sign-on ID tokens
    • For hosts, in exchange for cloud instance identity documents
  • Easily automate certificate management:

Whatever your use case, step-ca is easy to use and hard to misuse, thanks to safe, sane defaults.


Don't want to run your own CA? 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.


Questions? Find us in Discussions or Join our Discord.

Website | Documentation | Installation | Getting Started | Contributor's Guide

GitHub release Go Report Card Build Status License CLA assistant

GitHub stars Twitter followers

star us

Features

🦾 A fast, stable, flexible private CA

Setting up a public key infrastructure (PKI) is out of reach for many small teams. step-ca makes it easier.

Many ways to automate

There are several ways to authorize a request with the CA and establish a chain of trust that suits your flow.

You can issue certificates in exchange for:

🏔 Your own private ACME server

ACME is the protocol used by Let's Encrypt to automate the issuance of HTTPS certificates. It's super easy to issue certificates to any ACMEv2 (RFC8555) client.

👩🏽💻 An online SSH Certificate Authority

  • Delegate SSH authentication to step-ca by using SSH certificates instead of public keys and authorized_keys files
  • For user certificates, connect SSH to your single sign-on provider, to improve security with short-lived certificates and MFA (or other security policies) via any OAuth OIDC provider.
  • For host certificates, improve security, eliminate TOFU warnings, and set up automated host certificate renewal.

🤓 A general purpose PKI tool, via step CLI integration

Installation

See our installation docs here.

Documentation

Documentation can be found in a handful of different places:

  1. On the web at https://smallstep.com/docs/step-ca.

  2. On the command line with step help ca xxx where xxx is the subcommand you are interested in. Ex: step help ca provisioner list.

  3. In your browser, by running step help --http=:8080 ca from the command line and visiting http://localhost:8080.

  4. The docs folder is being deprecated, but it still has some documentation and tutorials.

Feedback?