Skip to content

Group F - Sprint 3 - Token Expiry, Notifications & Renewal#134

Merged
Charan-Nimmagadda merged 31 commits intomainfrom
GroupF/development
Apr 21, 2025
Merged

Group F - Sprint 3 - Token Expiry, Notifications & Renewal#134
Charan-Nimmagadda merged 31 commits intomainfrom
GroupF/development

Conversation

@kushi-3
Copy link
Contributor

@kushi-3 kushi-3 commented Apr 21, 2025

Sprint 3 Scope and Deliverables:

  • Cron job to fetch tokens expiring in 7 and 3 days.
  • Sending and logging reminder emails via Nodemailer.
  • Automatic deactivation of accounts with expired tokens.
  • Login API to detect deactivated users and prompt for token renewal.
  • Token renewal API to generate new tokens and send activation emails.
  • Activation of renewed tokens and re-enabling of user accounts.
  • Email-based renewal process (no UI required).
  • End-to-end and edge case testing for expiry and renewal.
  • Verification of logging, monitoring, and fallback error messages.

TheJob21 and others added 29 commits April 16, 2025 22:40
…ing-notification-system

Group f/token expiry monitoring notification system
Implemented student dashboard with conditional UI and navigation
});

// Redirect user based on role
if (role === "coordinator") {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do not remove the coordinator and supervisor-based navigation.
If any logic needs to be updated, adapt it accordingly without breaking role-based routing.
Alternatively, inform the respective team about the changes so they can adjust on their end.

Copy link
Contributor

@Aakash452 Aakash452 Apr 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The coordinator and supervisor-based navigation was never added from this side, I think it was a merge issue cause when I worked on student-dashboard navigation, there was no navigation logic for other roles

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that this wasn’t added from your side, but I just want to clarify that this is not a merge issue. The coordinator and supervisor-based navigation was added by Team A (I believe), and the logic does exist. So please either add the necessary navigation logic accordingly or inform the respective team, so they can make the required adjustments

});

// Redirect user based on role
if (role === "coordinator") {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that this wasn’t added from your side, but I just want to clarify that this is not a merge issue. The coordinator and supervisor-based navigation was added by Team A (I believe), and the logic does exist. So please either add the necessary navigation logic accordingly or inform the respective team, so they can make the required adjustments

@Charan-Nimmagadda Charan-Nimmagadda merged commit 053b5c3 into main Apr 21, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants