fix(auth): ScadaBridge 1.2 review fixes — secret-test repoint, checklist, Scope guard, 0.1.1 pin
This commit is contained in:
@@ -18,9 +18,10 @@
|
||||
- [ ] EF Core migrations have been applied (SQL script reviewed and executed)
|
||||
- [ ] `ScadaBridge:Security:JwtSigningKey` is at least 32 characters, randomly generated
|
||||
- [ ] **Both central nodes use the same JwtSigningKey** (required for JWT failover)
|
||||
- [ ] `ScadaBridge:Security:LdapServer` points to the production LDAP/AD server
|
||||
- [ ] `ScadaBridge:Security:LdapUseTls` is `true` (LDAPS required in production)
|
||||
- [ ] `ScadaBridge:Security:AllowInsecureLdap` is `false`
|
||||
- [ ] `ScadaBridge:Security:Ldap:Server` points to the production LDAP/AD server
|
||||
- [ ] `ScadaBridge:Security:Ldap:Transport` is `Ldaps` (LDAPS required in production)
|
||||
- [ ] `ScadaBridge:Security:Ldap:AllowInsecure` is `false`
|
||||
- [ ] LDAP service-account password supplied via env var `ScadaBridge__Security__Ldap__ServiceAccountPassword` (renamed from `ScadaBridge__Security__LdapServiceAccountPassword` in the Task 1.4 nested-config cutover)
|
||||
- [ ] LDAP search base DN is correct for the organization
|
||||
- [ ] LDAP group-to-role mappings are configured
|
||||
- [ ] Load balancer is configured in front of central UI (sticky sessions not required)
|
||||
|
||||
Reference in New Issue
Block a user