The server component of the PKI Vault responsible for storing and managing certificates and their keys.
- REST API for managing certificates and keys (mostly only insertion and retrieval of the latest version of a certificate with certain characteristics)
- Automatic linking of certificate chains and keys no matter in which order or when they are inserted
- Certificate subscriptions: Clients can subscribe to certificates with certain characteristics and can retrieve the latest usable version. Available characteristics are only subject alternative names + common name for now.
- Architecture support for multiple databases (only implementation is PostgreSQL at the moment)
The following databases and versions are supported and were tested:
- PostgreSQL >= 14.7
It is possible that other versions will work, but there is no guarantee.
If you need support for other databases consider creating a pull request with an implementation or open an issue. An example implementation can be found at internal/db/postgresql.
Currently, there is no release available or docker image, so you have to build the binary yourself.
Before you build the binary, you have to make sure all generated code is up-to-date. Execute the following commands to generate all code:
make generate-all
go buildNote: To generate all code the postgresql database must be running. See Development Code Generation for more information.
A development config file is provided at config.dev.yml and can be adapted to run the service.
The Http REST API of this server is generated from the spec at .openapi/openapi.yaml with strict types.
Currently, there are no pre-generated clients available for use. It is planned to provide these, but for now you have to generate them yourself. Code generators that can be used for this are for example openapi-generator.tech or oapi-codegen (Golang only)
- Golang >= 1.20
- Docker and Docker Compose or equivalent tools like Podman and Podman Compose for the dev containers
makeon Linux or an equivalent tool on other platforms
The server is built with a layered architecture in mind. The layers are as follows:
- REST API: The REST API layer is responsible for handling HTTP requests and responses. It is also responsible for authentication and authorization. Code resides in the internal/restserver package.
- Service: The service layer is responsible for handling business logic. It is the layer that is used by the REST API layer. Code resides in the internal/service package.
- Repository: The repository layer is responsible for handling database access. It is the layer that is used by the service layer. Code resides in the internal/db package.
Some code in this project gets generated from different sources. Here is an overview of generated code:
- GoMock: testing; generated at internal/mocks from different interfaces in the project
- Wire: dependency injection; generated at internal/wire from the dependency injection code in the same package
- OAPI Codegen: REST API with strict types; generated at internal/restserver/openapi.gen.go from the OpenAPI spec at .openapi/openapi.yaml
- SQLBoiler: per SQL database type structs for safe access; generated at internal/db from the database schema. The database must be online and must have all migrations applied for generation. It uses the credentials in .env to connect to the database.
The server uses certificates for testing. The generation script and certificate specifications can be found in testdata/certificates. The certificates are generated using cfssl.
Execute the following commands to set up the development environment:
docker compose -f docker-compose.dev.yml up -d
make migrate-postgresql generate-all go-testThis will start the development containers, run the database migrations and generate code and testdata certificates. It will also run the tests to verify that everything is working.