feat(auth): point dev clusters at shared GLAuth 10.100.0.35; retire local scadabridge-ldap
Both :9000 (docker) and :9100 (docker-env2) central nodes now bind the shared dev GLAuth (scadaproj/infra/glauth/, dc=zb,dc=local) via the cn=serviceaccount search account instead of the bundled scadabridge-ldap container (now commented out in infra/docker-compose.yml, kept for rollback). Verified: multi-role -> all 4 roles on both clusters with scadabridge-ldap stopped.
This commit is contained in:
@@ -23,13 +23,13 @@
|
||||
},
|
||||
"Security": {
|
||||
"Ldap": {
|
||||
"Server": "scadabridge-ldap",
|
||||
"Server": "10.100.0.35",
|
||||
"Port": 3893,
|
||||
"Transport": "None",
|
||||
"AllowInsecure": true,
|
||||
"SearchBase": "dc=zb,dc=local",
|
||||
"ServiceAccountDn": "cn=admin,dc=zb,dc=local",
|
||||
"ServiceAccountPassword": "password"
|
||||
"ServiceAccountDn": "cn=serviceaccount,dc=zb,dc=local",
|
||||
"ServiceAccountPassword": "serviceaccount123"
|
||||
},
|
||||
"JwtSigningKey": "scadabridge-env2-dev-jwt-signing-key-must-be-at-least-32-characters-long",
|
||||
"JwtExpiryMinutes": 15,
|
||||
|
||||
Reference in New Issue
Block a user