Vadym/obsidian
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

vault backup: 2026-04-28 19:26:46

Browse source
This commit is contained in:
Vadym Samoilenko 2026-04-28 19:26:46 +01:00
parent c4933ecbcc
commit d6016da8ff
2 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
01 Projects/oliver-sales-ops-platform/Oliver Sales Ops Platform.md
View file

@ -24,6 +24,10 @@ created: 2026-04-28
- **Local path:** `/Volumes/SSD/Projects/Oliver/oliver-sales-ops-platform`
## Sessions
### 2026-04-28 – How should SSO user access control
**Asked:** How should SSO user access control be implemented — separate Azure environment or backend allowlist with allowed emails?
**Done:** Implemented backend-based SSO access control with allowlist verification, redirect URL configured to https://optical-dev.oliver.solutions/oliver-sales-ops-platform/
### 2026-04-28 – How should SSO user access restrictions
**Asked:** How should SSO user access restrictions be implemented — separate Azure environment or backend allowlist validation?
**Done:** Confirmed backend allowlist approach is viable; reviewed AuthProvider.tsx and updated docstring in _upsert_app_user for clarity.
@ -32,6 +36,7 @@ created: 2026-04-28
## Change Log
| Date | Requested | Changed | Files |
|------|-----------|---------|-------|
| 2026-04-28 | SSO access control | Created allowlist service, added auth middleware with email verification, configured redirect URL | config/allowed_users.yaml, backend/app/services/allowlist.py, backend/app/middleware/auth.py |
| 2026-04-28 | SSO user restrictions | AuthProvider logic review, _upsert_app_user docstring update | AuthProvider.tsx, _upsert_app_user |
## Related

3
99 Daily/2026-04-28.md
View file

@ -110,3 +110,6 @@ tags: [daily]
- 19:24 | `oliver-sales-ops-platform`
- **Asked:** How should SSO user access restrictions be implemented — separate Azure environment or backend allowlist validation?
- **Done:** Confirmed backend allowlist approach is viable; reviewed AuthProvider.tsx and updated docstring in _upsert_app_user for clarity.
- 19:25 | `oliver-sales-ops-platform`
- **Asked:** How should SSO user access control be implemented — separate Azure environment or backend allowlist with allowed emails?
- **Done:** Implemented backend-based SSO access control with allowlist verification, redirect URL configured to https://optical-dev.oliver.solutions/oliver-sales-ops-platform/