Commit 43e40e1
Merge release-3.6.3 into main: data sync user validation (#461)
* fix: block data sync if user does not belong to same VAN
Added providerServiceMapID validation in data sync login flow.
After successful authentication, the data sync user's PSM is compared
against the main session's PSM. If they differ (e.g., Mysuru nurse
trying to sync a Vizag van), an alert is shown and sync is blocked.
- Alert: 'Data sync user does not belong to the same VAN'
- Clears serverKey so the sync screen remains locked
- Applies to both normal and concurrent-login (doLogout) flows
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Revert "fix: block data sync if user does not belong to same VAN"
This reverts commit 3ea1285.
* fix: validate data sync userID matches main session userID
Block data sync login if the authenticated data sync user is different
from the logged-in MMU session user. Compares userID from the
userAuthenticate API response against the session's stored userID.
Shows alert 'Sync user is not valid' and clears serverKey if mismatch.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Sneha <sneha@ADMINs-MacBook-Pro.local>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>1 parent e81ec5f commit 43e40e1
1 file changed
Lines changed: 17 additions & 0 deletions
Lines changed: 17 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
288 | 288 | | |
289 | 289 | | |
290 | 290 | | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
| 304 | + | |
| 305 | + | |
| 306 | + | |
| 307 | + | |
291 | 308 | | |
292 | 309 | | |
293 | 310 | | |
| |||
0 commit comments