OIDC Provider

Rationale

Many organizations want to consolidate the Sign in with Ethereum workflow to a single identity service (Identity Provider or IdP) that could be used to access all their federated services (Relying Parties or RPs) using OpenID Connect to forward the user's session. This reduces overhead and mitigates security risks by consolidating authentication to one protected site instead of several, especially in complex IT systems that have many services for their users to access.

Getting Started

The OIDC Provider implementation of Sign in with Ethereum can be found here:

signinwithethereum/siwe-oidc

→

Currently, two runtime modes are supported: (1) a standalone executable (using Axum and Redis) and (2) a WASM module within a Cloudflare Worker. Both are built from the same codebase, specializing at build time. Compilation with a cargo target of wasm32 will build for Cloudflare Worker deployments.

Demo

A demo site is available that demonstrates how the OIDC flow works in production

signinwithethereum/oidc-demo

→

Deployment Guide

This guide covers deploying the SIWE OIDC Provider in production environments. Choose from multiple deployment options based on your infrastructure needs.

Deployment Guide

→

Hosted Provider

Instructions for interacting with our deployed instance of the OpenID Connect Provider (OP) with SIWE

Hosted OIDC Provider

→