Directory · Authentication · Business Systems

Authentication that never stops,
built on field-proven engineering

Seojindsa designs and builds multi-factor authentication (MFA), SSO integration, large-scale account management, and ERP-integrated business systems around Yullin Directory Server, our own distribution of 389 Directory Server. Our architecture runs in production at a global enterprise's research center, and we have presented it at the international LDAP conference.

Capabilities

From directory to business systems, one team end to end

We don't stop at the design document. We build the plugins ourselves, tune performance down to the kernel and memory level, and hand over the operations tooling too.

Yullin Directory Server

Our 389 DS distribution · OpenLDAP · AD

We supply Yullin DS, our own directory server built on 389 Directory Server, and cover the full lifecycle: schema design, replication, access control, migration, and incident response.

MFA and OTP

privacyIDEA

We put OTP verification directly into the directory server's bind step, so existing LDAP applications get MFA without a single code change.

SSO and identity federation

Keycloak · AD FS · SAML · OIDC

We connect Keycloak and AD FS to bring systems with different account models under a single sign-on.

AI agent auth and policy

OAuth · OPA · Cedar

We give each AI agent its own identity and delegation tokens, and use the OPA and Cedar policy engines to authorize every request.

Performance tuning

LMDB · NUMA · Huge Pages

We analyze everything from storage engine internals to CPU cache behavior to hit response-time targets on large directories.

Operations automation

Bulk account creation, deletion, and recovery are jobs where one mistake is costly. We turn them into tools with safeguards built in.

ERP-integrated business systems

Next.js · Multi-tenant DB

We design and build multi-tenant commerce and operations platforms that read ERP data safely.

AI agent authentication · Policy-based authorization

Authenticate AI agents, not just people,
and govern them with policy

As AI agents and automation tools multiply inside a company, “who can do what” can no longer live scattered across your codebase. We layer the OPA and Cedar policy engines on top of the identity management expertise we built in directory and SSO work, so permissions for people, services, and agents are defined and verified in one place.

AI agent authentication

OAuth 2.x · Token Exchange · MCP

Each agent gets its own identity in the directory, and Keycloak issues it short-lived tokens. For agents acting on a user's behalf, the delegation scope is carried in the token, so an agent never holds more privilege than the person it serves. We also set up authorization for MCP servers.

OPA (Open Policy Agent)

Rego · Kubernetes · API Gateway

With OPA, a general-purpose policy engine, we manage API gateway, microservice, and Kubernetes deployment-approval policies as code. Moving policy out of the application makes auditing and changes far easier.

Cedar policy language

RBAC + ABAC · Policy verification

We use Cedar, a highly readable policy language, to design fine-grained application permissions that combine roles and attributes. Policies can be analyzed and verified before deployment, catching permission mistakes before they reach production.

  • Per-agent identity and credential issuance and revocation, with usage auditing
  • Existing LDAP groups and attributes feed policy directly — no second source of truth for permissions
  • Policy repository, testing, and deployment pipeline (Policy as Code)

Case studies

Systems we built and still run

Customer names are withheld in line with their security policies. The architecture and engineering decisions are presented as is.

In production · Presented internationally

MFA by integrating 389 Directory Server directly with privacyIDEA

Customer
A global electronics company's overseas R&D center
Challenge
Roll out multi-factor authentication across every existing system that uses LDAP
Solution
Developed a pre-bind plugin for 389 DS that verifies OTPs with privacyIDEA during the bind itself, eliminating intermediate translation layers such as a separate IdP
Result
MFA with zero application changes and a simpler authentication path
389 DSCprivacyIDEASTARTTLS
SSO integration

AD FS + Keycloak Claims Provider integration

Challenge
AD has one account per user, while 389 DS and Keycloak allow several per user. Both models had to share a single SSO
Solution
Added Keycloak to AD FS as a Claims Provider Trust, so signing in with Keycloak (a 389 account) also signs users in to AD SSO-integrated products automatically
Result
N:1 account mapping solved at the authentication layer [enter status/results]
AD FSKeycloakSAMLOIDC389 DS
Performance tuning

389 DS / LMDB in-memory disk performance analysis

Challenge
Directory performance fell short of expectations even on a RAM disk (tmpfs)
Analysis
Traced the cause to LMDB's mmap, B+tree, and copy-on-write design amplifying L3 cache misses on tmpfs
Solution
Step-by-step tuning of numactl NUMA binding, Huge Pages, CPU affinity, LMDB cache, and BIOS settings
LMDBNUMAHuge PagesLinux
Operations tooling

LDAP bulk account deletion and recovery tool

Challenge
Clean up users scattered across multiple OUs, including every group and automount reference
Solution
Handles posixAccount, posixGroup, group membership, and automount entries together. Takes timestamped LDIF backups before deletion and ships with recovery scripts
Safety
Runs as a dry check by default; deletes only when you pass --do-it
PerlNet::LDAPLDIFShell
Business systems

OneDesk — multi-tenant store + ERP integration platform

Scope
Multi-tenant DB design, Next.js frontend, legacy data migration, an automated pipeline from order to review, and product spec extraction from images
Principle
ERP access is read-only, by design from day one
Speed
Built in about one week with AI pair programming (June 2026)
Next.jsMulti-tenantERPAI pipeline
How we build

AI multi-agent development workflow

What
An in-house development harness with Claude as orchestrator and multiple coding agents splitting implementation and review
Strength
People own domain knowledge and layered design; agents handle repetitive implementation, cutting delivery times dramatically
Training
Authored Korean-language textbooks and lab guides on harness engineering
Claude CodeCodexWSL2Multi-agent

Research and talks

Field-tested architecture, proven on the international stage

LDAPCon 2026 · Oct 8, 2026 · Museum Uhlandsaal · 40-minute talk

Enterprise Case Study: Direct Integration of 389 Directory Server with PrivacyIDEA

We presented an architecture that verifies OTPs right inside 389 Directory Server through a pre-bind plugin, walked through a real enterprise deployment, and demonstrated it live. Speaker: Sangjun Song (Seojindsa / Gachon University)

View slides (PDF)

MFA without the middle layer

The common approach puts a translation layer, such as a separate IdP or RADIUS, in front of applications. We made the directory server verify the OTP the moment it receives the bind, cutting both points of failure and components to operate.

Company

Seojindsa

We are experts in all modern Directory Servers and directory system log analytics using open source.Since 2008, Seojindsa has specialized in the full range of modern directory servers and open-source log analytics for directory systems. Together with AboutDAP, our dedicated directory technology brand, we deliver technical support and training.

2008

Founded

LDAPCon 2026

International conference speaker

10+

Customers deployed and supported

Gachon University

Industry–academia research

Start a project

Tell us about your environment

Share your current directory product, user count, and the systems you need to integrate. An engineer will review it personally and get back to you.

520 Misa-daero, Building D, Unit 537, Hanam-si, Gyeonggi-do, Republic of Korea
Phone +82-70-8832-0594
Email sales@seojindsa.kr