From 58235bfdb1d02afd89e889a75b8d7ac0916cbeed Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Thu, 29 Jan 2026 19:24:42 -0800 Subject: [PATCH] OIDC: document ECDSA signing method support --- Cryptography-and-FIPS-Compliance.md | 2 ++ OIDC-Integration.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/Cryptography-and-FIPS-Compliance.md b/Cryptography-and-FIPS-Compliance.md index 4352e54..bba8257 100644 --- a/Cryptography-and-FIPS-Compliance.md +++ b/Cryptography-and-FIPS-Compliance.md @@ -24,6 +24,7 @@ SeaweedFS uses Go's standard library cryptographic packages (`crypto/*`) for all | S3 Signature V4 | HMAC-SHA256 | AWS-compatible request signing | | S3 Signature V2 | HMAC-SHA1 | Legacy AWS signature support | | JWT Tokens | HMAC-SHA256 | For volume server and filer access control | +| OIDC Tokens | RSA, ECDSA | For OIDC identity provider integration | | SSE-C Key Validation | MD5 | For key integrity verification (AWS S3 compatible) | ### Transport Encryption (In Transit) @@ -45,6 +46,7 @@ All cryptographic algorithms used by SeaweedFS are **FIPS-approved**: | SSE-C Encryption | AES-256-CTR | ✅ Approved | | S3 Signatures | HMAC-SHA256 | ✅ Approved | | Hashing | SHA-256 | ✅ Approved | +| OIDC Validation | RSA, ECDSA | ✅ Approved | | Transport | TLS 1.2/1.3 | ✅ Approved | | Legacy S3 Signatures | HMAC-SHA1 | ⚠️ Approved (use V4 preferred) | | SSE-C Key Validation | MD5 | ⚠️ Used for AWS S3 compatibility only | diff --git a/OIDC-Integration.md b/OIDC-Integration.md index c1158d5..7d0c25d 100644 --- a/OIDC-Integration.md +++ b/OIDC-Integration.md @@ -10,7 +10,7 @@ This guide shows how to integrate OpenID Connect (OIDC) identity providers with SeaweedFS S3 Gateway using the advanced IAM and STS configuration. It supports: -- Direct OIDC authentication to S3 with Bearer tokens +- Direct OIDC authentication to S3 with Bearer tokens (RSA and ECDSA) - OIDC to STS role assumption using trust policies and role mapping ## Supported Identity Providers