[MN-04] Identity: Google Callback Lack Error Handling #3

Open
opened 2026-05-05 12:15:03 +00:00 by mjasin · 0 comments
Owner

Full Detail: The Google OAuth callback in Program.cs (lines 354-383) uses simple redirects with query string error codes (error=ExternalLoginFailed, error=ProvisioningFailed). This provides poor UX as these errors are not surfaced meaningfully to the user.

Action:

  • Implement logging for createResult.Errors if user provisioning fails.
  • Ensure the Login page (UI.Shared) has logic to catch these query parameters and display descriptive, user-friendly error messages (e.g., 'User with this email already exists' instead of generic 'ProvisioningFailed').
**Full Detail:** The Google OAuth callback in `Program.cs` (lines 354-383) uses simple redirects with query string error codes (`error=ExternalLoginFailed`, `error=ProvisioningFailed`). This provides poor UX as these errors are not surfaced meaningfully to the user. **Action:** - Implement logging for `createResult.Errors` if user provisioning fails. - Ensure the Login page (`UI.Shared`) has logic to catch these query parameters and display descriptive, user-friendly error messages (e.g., 'User with this email already exists' instead of generic 'ProvisioningFailed').
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mjasin/Nexus.Reader#3