Skip to content
Projects

arturoeanton/goscim has 30 GitHub stars and 5 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 16:48 UTC. Last push 2026-11-13.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
Update delayed
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

🚀 Lightning-fast SCIM 2.0 server in Go that makes identity management simple and scalable. Built for developers who need enterprise-grade user provisioning without the enterprise complexity.

Developer Tools

README.md

Original

GoSCIM

CI Go Report Card Go Reference MIT License Release

A SCIM 2.0 server in Go, backed by Couchbase.

Resource types, schemas and per-attribute permissions are JSON files, so adding a resource type takes no code. Authentication is required, filter values are bound rather than interpolated into queries, and permissions are enforced per attribute on both read and write.

Using PostgreSQL instead of Couchbase? See the sister project go-vorpal-scim.

Quick start

With Docker Compose (starts Couchbase, initialises the cluster, and starts GoSCIM):

git clone https://github.com/arturoeanton/goscim.git && cd goscim
docker compose up -d --build

Or running the binary directly against a local Couchbase container:

docker run -d --name goscim-db -p 8091-8094:8091-8094 -p 11210:11210 \
  couchbase:community-7.1.1
# Set up the cluster at http://localhost:8091 with the credentials below.

export SCIM_AUTH=basic                       # how clients authenticate
export SCIM_BASIC_USERS='admin:secret:admin'
export SCIM_ADMIN_USER=Administrator         # how the server reaches Couchbase
export SCIM_ADMIN_PASSWORD=password
export SCIM_COUCHBASE_TLS=false              # local cluster, no certificate

go run .
curl -s -u admin:secret -X POST http://localhost:8080/scim/v2/Users \
  -H 'Content-Type: application/scim+json' \
  -d '{"schemas":["urn:ietf:params:scim:schemas:core:2.0:User"],
       "userName":"[email protected]",
       "emails":[{"value":"[email protected]","type":"work","primary":true}],
       "active":true}'

201 Created, with the resource in the body, its URI in Location and its revision in ETag.

SCIM_AUTH has no default: the server refuses to start until you pick jwt, basic, or none. Full walkthrough in getting started.

What it does

  • CRUD, search (GET and POST /.search), bulk operations (POST /Bulk), filtering, sorting, pagination and attribute projection (attributes / excludedAttributes) over RFC 7643/7644
  • Group membership synchronisation: Group.members changes automatically materialise User.groups (direct and indirect nested memberships, cycle-safe) and clean up dangling references when users or groups are deleted
  • Complex array value filters: emails[type eq "work"] and emails[type eq "work"].value in both search (GET / POST /.search) and PATCH (add, replace, remove), compatible with Microsoft Entra ID and Okta
  • Discovery: ServiceProviderConfig, ResourceTypes, Schemas, derived from the running code rather than a file that can drift from it
  • Authentication: OAuth 2.0 access tokens (RFC 9068) verified against a JWKS (RS256/384/512, ES256/384/512, EdDSA), HTTP Basic for development, or an explicit anonymous mode
  • Authorization per attribute: $reader / $writer role lists alongside SCIM's own mutability, returned and atomic uniqueness
  • Structured audit logging: log/slog audit trail (SCIM_AUDIT_LOG) with X-Request-Id correlation, caller subject / roles, action and outcome
  • Password hashing: password is hashed with Argon2id by default (SCIM_PASSWORD_MODE: argon2id, bcrypt, reject, or plain)
  • Concurrency control: ETag with If-Match and If-None-Match, plus atomic Couchbase KV sentinel locks closing uniqueness TOCTOU races
  • Health and readiness: /healthz and /readyz (probing Couchbase KV and Query services), plus a distroless multi-stage Dockerfile
  • Schema-driven everything: add a resource type by dropping in two JSON files and restarting

What it does not do

Worth knowing before you invest time:

  • Prometheus metrics endpoint

The 1.0 audit records why it is open and roughly what it would take.

Adding a resource type

Two files, no code:

// config/schemas/urn+ietf+params+scim+schemas+custom+2.0+Device.json
{
  "id": "urn:ietf:params:scim:schemas:custom:2.0:Device",
  "name": "Device",
  "attributes": [
    { "name": "serialNumber", "type": "string",
      "required": true, "uniqueness": "server", "mutability": "immutable" }
  ]
}
// config/resourceType/Device.json
{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:ResourceType"],
  "id": "Device", "name": "Device", "endpoint": "/Devices",
  "schema": "urn:ietf:params:scim:schemas:custom:2.0:Device",
  "schemaExtensions": []
}

Restart, and /scim/v2/Devices exists with CRUD, GET and POST /.search, automatic inclusion in root POST /scim/v2/.search and POST /scim/v2/Bulk, its own bucket, and serialNumber enforced unique and refused on update.

Filters

userName eq "bjensen"
name.familyName co "O"
title pr and userType eq "Employee"
emails[type eq "work" and primary eq true]
emails[type eq "work"].value ew "@example.com"
userType eq "Employee" and (emails co "example.com" or emails co "example.org")
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.department eq "Sales"

All RFC 7644 operators — eq ne co sw ew gt ge lt le pr, and or not, ( ), and [ ] complex array value filters. Values are passed to Couchbase as bound parameters and never enter the query text; a filter that fails to parse is refused rather than translated.

Documentation

Getting started A running server and your first user
Installation Couchbase, building, deploying
Configuration Every variable and config file
API reference Endpoints, payloads, status codes, filters
Schemas and permissions Attributes, and who may read or write them
Architecture How it fits together, and why
Security Threat model and hardening checklist
Operations Signals, consistency, troubleshooting
Development Building, testing, code layout
Changelog Releases and breaking changes

Requirements

Go 1.26+ (toolchain 1.27.4+) to build. Couchbase 7.x, Community or Enterprise, with the data, query and index services.

Development

make check        # build, vet, unit suite with the race detector
make integration  # the suite against a real Couchbase, in a container
make cover        # coverage

The unit suite runs the real router over an in-memory store; the integration suite starts Couchbase in a container and drives the same server through it. Contributions are welcome — see CONTRIBUTING, and RELEASE-1.0 for what is open.

Status

1.2.0. The test suite covers the request path end to end, and the integration suite exercises it against a real Couchbase. It has not yet been run against a production identity provider such as Okta or Entra ID; if you do, reports are welcome — that is where the remaining interoperability gaps will show up.

License

MIT.