OpenID Connect Identity Provider (Login and Consent part) using client certificate authentication and ORY Hydra
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Jan Dittberner cdaed2f4e4 Prepare changelog for 0.4.0 release 2 months ago
cmd/idp Reduce minimum CSRF key length to 256 bits 2 months ago
debian Run deb-systemd-helper in postinst 12 months ago
docs Improve documentation and defaults 1 year ago
internal Fix linter warnings 2 months ago
translations Fix subject handling for login requests 2 months ago
ui Remove copyright years from base template 2 months ago
.gitignore Implement consent management 12 months ago
.golangci.yml Update golangci-lint, fix warnings 2 months ago
.goreleaser.yml Add packaging configuration 1 year ago
LICENSE.txt Add Apache License 2.0 text 1 year ago
Makefile Implement consent management 12 months ago Fix subject handling for login requests 2 months ago Prepare changelog for 0.4.0 release 2 months ago
go.mod Switch logging to slog 2 months ago
go.sum Switch logging to slog 2 months ago

CAcert OAuth2 / OpenID Connect IDP

This repository contains an implementation for an identity provider. ORY Hydra is used for the actual OAuth2 / OpenID Connect operations. The implementation in this repository provides the end user UI components that are required by Hydra to allow login and consent.

The code in this repository is licensed under the terms of the Apache License Version 2.0.

Copyright © 2020-2023 Jan Dittberner



You need a set of certificate and private key and a PEM file with CA certificates used to verify client certificates to run cacert-idp.

An easy way to generate server certificate and key for local testing is mkcert.

  1. Run mkcert to generate idp.cacert.localhost+1.pem and idp.cacert.localhost+1-key.pem:

    mkcert -cert-file idp.cacert.localhost login.cacert.localhost
  2. Copy CA certificate for client certificates

    (curl -s ; \
     curl -s ) > client_ca.pem

Configure IDP

The Identity Provider application (IDP) requires a strong random key for its CSRF cookie. You can generate such a key using the following openssl command:

openssl rand -base64 32

Use this value to create idp.toml:

csrf.key = "<32 bytes of base64 encoded data>"


Now you can start the IDP:

go run cmd/idp.go


This application uses go-i18n for internationalization (i18n) support.

The translation workflow needs the go18n binary which can be installed via

go install

To extract new messages from the code run

goi18n extract -outdir translations .

Then use

goi18n merge -outdir translations translations/active.*.toml

to create TOML files for translation as translate.<locale>.toml. After translating the messages run

goi18n merge active.*.toml translate.*.toml

to merge the messages back into the active translation files. To add a new language you need to add the language code to the languages configuration option (default is defined in the configmap in cmd/idp.go).