Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
var /
git /
cesa-v3 /
docs /
specs /
Delete
Unzip
Name
Size
Permission
Date
Action
echasl23-admin-login-design.md
1.89
KB
-rw-r--r--
2026-05-18 12:51
echasl23-admin-login-requirements.md
2.43
KB
-rw-r--r--
2026-05-18 12:51
mail-queue-monitor-design.md
2.64
KB
-rw-r--r--
2026-05-18 12:51
mail-queue-monitor-requirements.md
2.04
KB
-rw-r--r--
2026-05-18 12:51
member-portal-login-design.md
2.41
KB
-rw-r--r--
2026-05-20 09:05
member-portal-login-requirements.md
1.48
KB
-rw-r--r--
2026-05-20 09:05
member-transformation-declaration-design.md
2.84
KB
-rw-r--r--
2026-05-20 09:05
member-transformation-declaration-requirements.md
2.02
KB
-rw-r--r--
2026-05-20 09:05
Save
Rename
# Member portal login (V3) — requirements ## Context CESA members authenticate on the public site via `user_login` (see cesa-main `php/memberportal.php`). V3 must accept the same credentials at `/login` without a separate PIN step on V3. ## Requirements 1. **Authentication** — Members may sign in with existing `user_login.username` and `user_login.password` (plain-text or `crypt`+`salt` when salt is set). 2. **Provider order** — Chain: `user_list`, then `member_portal` (`user_login`), then `echasl23`. 3. **Role** — Successful member portal authentication assigns `ROLE_MEMBER_FIRM` (and base frontend roles). 4. **Member firm check** — Before login succeeds, resolve `MemberContacts` → office → `tblMemberFirms` for the login’s `contact_id`. Reject login when no firm or `member_status` not in `Member`, `Testing`, `Retired` (aligned with legacy portal). 5. **Session** — Store `member_firm_id` and `member_firm_present` in session values after login. 6. **Transformation portal** — Mandated principals logging in via `user_login` may use `/member-firm/transformation` when their contact is flagged `MandatedPrincipal` and linked to an active member firm. ## Out of scope - Email PIN second factor on V3 (remains on legacy WordPress portal only). - Drupal `users` fallback. ## Acceptance criteria - Valid `user_login` with linked member firm authenticates and has `ROLE_MEMBER_FIRM`. - Login without a linked firm is rejected. - `user_list` and `echasl23` logins behave as before.