Files
scadaproj/ZB.MOM.WW.Auth
..

ZB.MOM.WW.Auth

Authentication and authorisation libraries for the ZB.MOM.WW SCADA family (OtOpcUa, MxAccessGateway, ScadaBridge). These are libraries, not a service — each package is linked directly into the consuming application at build time. There is no central authentication process or network hop; auth logic runs in-process alongside the application.


Packages

Package Description Key Dependencies
ZB.MOM.WW.Auth.Abstractions Auth contracts, canonical role constants, and shared types (LdapOptions, LdapAuthResult, ILdapAuthService, IApiKeyStore). No runtime dependencies beyond the BCL.
ZB.MOM.WW.Auth.Ldap LDAP authentication service: bind-then-search-then-bind against GLAuth or Active Directory; RFC 4514-aware group extraction; fail-closed. Abstractions, Novell.Directory.Ldap.NETStandard
ZB.MOM.WW.Auth.ApiKeys SQLite-backed API-key store with pepper-based PBKDF2 hashing, rotation, and audit log. Includes a MigrationHostedService that runs schema migrations on startup. Abstractions, Microsoft.Data.Sqlite
ZB.MOM.WW.Auth.AspNetCore ASP.NET Core DI helpers (AddZbAuth), cookie defaults, claim-type constants, and LdapOptionsValidator registration. Wires together Ldap + ApiKeys + cookie middleware. Abstractions, Ldap, ApiKeys, Microsoft.AspNetCore.App

Consumer Matrix

Consumer Abstractions Ldap ApiKeys AspNetCore
OtOpcUa yes yes yes
MxAccessGateway yes yes yes yes
ScadaBridge yes yes yes yes

ApiKeys is NOT used by OtOpcUa (that app authenticates human operators via LDAP + cookies only; machine-to-machine access is out of scope).


Versioning

All four packages are versioned lockstep from Directory.Build.props. The current release is 0.1.0. A single version bump in Directory.Build.props bumps all four packages simultaneously — consumers should reference the same version for all ZB.MOM.WW.Auth packages.


Running the opt-in LDAP integration test

The GLAuth integration test (GLAuthIntegrationTests) is skipped by default and does not affect the normal test run. To exercise it against a live GLAuth instance:

  1. Start the GLAuth Docker stack from the sibling repo:

    cd ~/Desktop/ScadaBridge/infra/glauth
    docker compose up -d
    
  2. Set the required environment variables and run the test:

    export ZB_LDAP_IT=1
    export ZB_LDAP_SVC_DN="cn=svc,dc=lmxopcua,dc=local"
    export ZB_LDAP_SVC_PW="svcpass"
    export ZB_LDAP_USER="alice"
    export ZB_LDAP_PW="alicepass"
    
    dotnet test tests/ZB.MOM.WW.Auth.Ldap.Tests \
      --filter "FullyQualifiedName~GLAuthIntegrationTests"
    

All other variables (ZB_LDAP_SERVER, ZB_LDAP_PORT, ZB_LDAP_BASE, ZB_LDAP_USERATTR) default to sensible GLAuth values and are optional. The test also probes TCP reachability before attempting auth and skips if the server is not contactable.


Publishing packages

Use build/push.sh to pack and push to the Gitea NuGet feed:

export GITEA_NUGET_SOURCE="https://gitea.dohertylan.com/api/packages/dohertj2/nuget/index.json"
export GITEA_NUGET_KEY="your-gitea-token"
./build/push.sh

The script runs dotnet pack -c Release then dotnet nuget push --skip-duplicate.


Design documentation

Full design docs live in the components/auth folder of the SCADA project notes:

  • ~/Desktop/scadaproj/components/auth/spec/SPEC.md — overall auth specification
  • ~/Desktop/scadaproj/components/auth/spec/CANONICAL-ROLES.md — role taxonomy
  • ~/Desktop/scadaproj/components/auth/shared-contract/ — shared contract types