Custom OAuth Provider (oauthd) Deployment

Overview

A containerized OAuth daemon (oauthd) configured with a custom identity provider, backed by Redis, to issue and manage OAuth flows for an internal “wave” platform.

Why It Exists

Integrating third-party and custom OAuth providers in one place is easier with a dedicated OAuth gateway. oauthd centralizes provider definitions and token exchange so applications don’t each re-implement OAuth.

What We Built

A Docker Compose stack building an oauthd instance (from an oauthd-instance base image) on port 6284, with a Redis service configured for append-only persistence. A custom provider package (wave/) mounts into oauthd’s providers directory and supplies the provider’s conf.json, settings.json, branding assets, and a me.js profile-mapping script pointing at the platform’s auth host.

Technologies & Approach

oauthd as the OAuth gateway; a hand-authored provider definition to plug a bespoke auth backend into the standard OAuth flow; Redis for token/session persistence; Docker Compose for reproducible deployment and service linking.

Outcome / Impact

A working, self-hosted OAuth gateway with a custom provider, demonstrating identity-integration and auth-infrastructure skills early on.

Capabilities Demonstrated

• Authoring custom OAuth provider definitions for a gateway (oauthd)
• Deploying auth infrastructure with Docker Compose and Redis
• Mapping a bespoke identity backend into a standard OAuth flow