Skill v1.0.0

currentAutomated scan100/100

golemcloud/golem/golem-add-http-auth-moonbit

──Details

PublishedOctober 22, 2026 at 10:55 PM

Content Hashsha256:9769d4d5727464e6...

Git SHA8c91bb815e81

──Files

Files (1 file, 3.2 KB)

SKILL.md3.2 KBactive

SKILL.md · 126 lines · 3.2 KB

version: "1.0.0" name: golem-add-http-auth-moonbit description: "Enabling authentication on HTTP endpoints in MoonBit Golem agents. Use when the user asks to add auth, security, or access control to HTTP endpoints."

Enabling Authentication on MoonBit HTTP Endpoints

Overview

Golem supports authentication on HTTP endpoints via OIDC providers. Authentication is enabled in the agent code and configured via security schemes in golem.yaml. Load the golem-configure-api-domain skill for details on setting up security schemes and domain deployments, including when to use subdomain versus domain.

Enabling Auth on All Endpoints (Mount Level)

Set #derive.mount_auth(true) on the agent struct to require authentication for all endpoints:

moonbit

#derive.agent
#derive.mount("/secure/{name}")
#derive.mount_auth(true)
pub(all) struct SecureAgent {
  name : String
}
 
fn SecureAgent::new(name : String) -> SecureAgent {
  { name }
}

Note: when #derive.mount_auth is not specified, authentication defaults to disabled.

Enabling Auth on Individual Endpoints

Set #derive.endpoint_auth(true) on specific endpoint methods:

moonbit

#derive.agent
#derive.mount("/api/{name}")
#derive.mount_auth(false)
pub(all) struct ApiAgent {
  name : String
}
 
fn ApiAgent::new(name : String) -> ApiAgent {
  { name }
}
 
#derive.endpoint(get="/public")
pub fn ApiAgent::public_data(self : Self) -> String {
  "public"
}
 
#derive.endpoint(get="/private")
#derive.endpoint_auth(true)
pub fn ApiAgent::private_data(self : Self) -> String {
  "private"
}

Overriding Mount-Level Auth

Per-endpoint #derive.endpoint_auth overrides the mount-level #derive.mount_auth setting:

moonbit

#derive.agent
#derive.mount("/api/{name}")
#derive.mount_auth(true)
pub(all) struct MostlySecureAgent {
  name : String
}
 
fn MostlySecureAgent::new(name : String) -> MostlySecureAgent {
  { name }
}
 
///|
/// No auth required (overrides mount-level auth)
#derive.endpoint(get="/health")
#derive.endpoint_auth(false)
pub fn MostlySecureAgent::health(self : Self) -> String {
  "ok"
}
 
///|
/// Auth required (inherited from mount)
#derive.endpoint(get="/data")
pub fn MostlySecureAgent::get_data(self : Self) -> String {
  "secret data"
}

Accessing the Authenticated Principal

When auth is enabled, add a Principal parameter to the new constructor or endpoint methods to receive the authenticated identity. The SDK automatically injects the principal value:

moonbit

#derive.agent
#derive.mount("/api/{name}")
#derive.mount_auth(true)
pub(all) struct AuthedAgent {
  name : String
  principal : Principal
}
 
fn AuthedAgent::new(name : String, principal : Principal) -> AuthedAgent {
  { name, principal }
}

Deployment Configuration

After enabling auth in code, you must configure a security scheme in golem.yaml. Load the golem-configure-api-domain skill for the full details, including when to use subdomain versus domain. Quick reference:

yaml

httpApi:
  deployments:
    local:
    - subdomain: my-app  # resolves to my-app.localhost:9006 by default
      agents:
        SecureAgent:
          securityScheme: my-oidc            # For production OIDC
        # or for development:
        # SecureAgent:
        #   testSessionHeaderName: X-Test-Auth

All versions