dohertj2/scadaproj
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects Releases Wiki Activity

[infra/glauth] Enable LDAPS/StartTLS on the shared GLAuth (unblocks mxaccessgw#180) #19

New Issue
Open
opened 2026-11-06 15:25:59 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:25:59 -05:00
Owner
Copy Link
Copy Source

The shared dev GLAuth (zb-shared-glauth, 10.100.0.35:3893) serves plain LDAP only: infra/glauth/config.toml has [ldaps] enabled = false (verified 2026-11-06). mxaccessgw review finding SEC-37 / R21-X1 (mxaccessgw#180) wants the deployed gateway to run with TLS to the directory in Production, and is blocked on the shared directory offering TLS. The redundant local pair (zb-ldap-primary/backup) would need the same.

Scope: generate/mount a cert, enable [ldaps] (or StartTLS), update README + client config examples, confirm each app's Auth config (Transport) still binds.

Source: mxaccessgw archreview/2026-10-21/remediation/00-tracking.md R21-X1 (surfaced during the 2026-11-06 backlog migration).

The shared dev GLAuth (zb-shared-glauth, 10.100.0.35:3893) serves plain LDAP only: infra/glauth/config.toml has [ldaps] enabled = false (verified 2026-11-06). mxaccessgw review finding SEC-37 / R21-X1 (mxaccessgw#180) wants the deployed gateway to run with TLS to the directory in Production, and is blocked on the shared directory offering TLS. The redundant local pair (zb-ldap-primary/backup) would need the same. Scope: generate/mount a cert, enable [ldaps] (or StartTLS), update README + client config examples, confirm each app's Auth config (Transport) still binds. Source: mxaccessgw archreview/2026-10-21/remediation/00-tracking.md R21-X1 (surfaced during the 2026-11-06 backlog migration).
dohertj2 added the type:infrapriority:p2cross-repomigrated labels 2026-11-06 15:25:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label cross-repo migrated priority:p2 type:infra
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/scadaproj#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?