← Complete project index

Infrastructure & Operations / Built / deployed

Central Secret Lifecycle / OpenBao

Two-tier OpenBao secret authority with Raft state, Transit auto-unseal, TLS, AppRole and a migration path away from filesystem secrets.

STATUSBuilt / deployed
AREAInfrastructure & Operations
STACK6 documented technologies
INTEGRATIONS2 connected / bounded services
01

OVERVIEW

What I built.

Two-tier OpenBao secret authority with Raft state, Transit auto-unseal, TLS, AppRole and a migration path away from filesystem secrets.

01

Built a two-tier OpenBao secret-control plane using Raft and Transit auto-unseal.

02

Configured TLS, AppRole/ACL boundaries, certificate-based operator access and a migration path away from flat filesystem secrets.

03

Kept the temporary same-host seal trust anchor explicit rather than presenting it as the final security boundary.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Main OpenBao -> Transit seal service for auto-unseal.

02
Architecture boundary

Raft provides durable service state; application identities consume scoped secret paths via reviewed auth methods.

03
Architecture boundary

A future independent seal host/KMS can replace the temporary local trust anchor without changing consumer paths.

03

NETWORK / DATA FLOW

What talks to what.

04

TECHNOLOGY STACK

The technical surface.

01OpenBao
02Raft
03Transit
04TLS
05AppRole
06Docker
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Main OpenBao -> Transit seal service for auto-unseal.

  2. 02

    Raft provides durable service state; application identities consume scoped secret paths via reviewed auth methods.

  3. 03

    A future independent seal host/KMS can replace the temporary local trust anchor without changing consumer paths.

06

TESTING & VALIDATION

How I know it works.

TEST 01

TLS-only access

TEST 02

Self-initialization path

TEST 03

Transit auto-unseal behavior

TEST 04

AppRole / ACL scope

TEST 05

Certificate operator access

TEST 06

No-root-token bootstrap behavior

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

CORECentral Secret Lifecycle / OpenBao
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01Raft configuration
02Transit seal topology
03ACL/AppRole definitions
04Canary secret
05TLS material boundaries
06DR inclusion policy
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

Current same-host static seal key is a temporary trust anchor

Seal service publishes no host port

Filesystem-secret migration remains staged until consumers are accepted

10

RESULT / CURRENT STATE

What this produced.

A production-style secrets lifecycle with explicit trust boundaries and a clear path to stronger physical separation.