Updated SeaweedFS Iceberg Catalog (markdown)

SeaweedFS-Iceberg-Catalog.md

@@ -8,7 +8,7 @@ The SeaweedFS S3 Tables feature implements the **Iceberg REST Catalog API**. Thi
 
 - **Iceberg REST Catalog**: Available on a dedicated port (default `8181`)
 - **S3 Data Access**: Available on the S3 port (default `8333`)
-- **Authentication**: SigV4 (Spark, Trino, RisingWave), OAuth2 (DuckDB, Doris), or unsigned REST + S3 access keys (Dremio)
+- **Authentication**: SigV4 (Spark, Trino, RisingWave), OAuth2 (DuckDB, Doris, OLake Go), or unsigned REST + S3 access keys (Dremio)
 
 ## Catalog and Bucket Relationship
 
@@ -53,6 +53,8 @@ See the integration guide for your engine below.
 | **Apache Doris** | OAuth2 | [[Doris Iceberg Integration]] |
 | **RisingWave** | SigV4 | [[RisingWave Iceberg Integration]] |
 | **Lakekeeper** | STS + SigV4 | [[Lakekeeper Iceberg Integration]] |
+| **OLake** | OAuth2 | [OLake Iceberg Integration](https://github.com/seaweedfs/seaweedfs/wiki/OLake-Iceberg-Integration) |
+
 
 ## Metadata Storage
 
@@ -81,7 +83,7 @@ SeaweedFS supports two authentication methods for the Iceberg REST Catalog:
 
 **SigV4 (Spark, Trino, RisingWave)** — Clients sign each request using AWS Signature Version 4. This is the standard method used by most Iceberg-compatible engines.
 
-**OAuth2 (DuckDB, Doris)** — Clients exchange S3 credentials for a bearer token via `POST /v1/oauth/tokens` using the `client_credentials` grant type. The S3 access key is used as `client_id` and the secret key as `client_secret`.
+**OAuth2 (DuckDB, Doris, Olake)** — Clients exchange S3 credentials for a bearer token via `POST /v1/oauth/tokens` using the `client_credentials` grant type. The S3 access key is used as `client_id` and the secret key as `client_secret`.
 
 ### Credential Vending