W04 Team Activity: Coordinate Authentication Work
Overview
- Purpose: Coordinate your work with your team.
- Task: Follow the instructions below to complete this week's team activity.
This week, your team will coordinate authentication work. Authentication features often depend on shared configuration, shared middleware, and shared expectations about signed-in and signed-out behavior.
Decide how you will coordinate
You may meet live with your team. If your schedules do not allow that, complete the same coordination process by posting messages in your Microsoft Teams channel.
Professional teams often span multiple countries and coordinate in both of these ways as well.
Activity Instructions
Follow up on code reviews and outstanding pull requests
- Open the team's GitHub repository.
- Review the list of open pull requests from the previous week.
- Identify any pull requests that are still waiting for review.
- Make a plan for who will review each outstanding pull request.
- Post in Microsoft Teams so the team knows who is reviewing each pull request.
- Identify any pull requests that have been approved but not merged yet.
- Make sure approved pull requests are merged or that the team has a clear plan for getting them merged.
Review the new assignment features
Open the Week 04 assignment and review the single list of five feature sets. Each person will own one feature set.
Choose features without duplicating work
- Assign one feature set to each team member; do not assign the same feature set to more than one person.
- Assign Feature Set 1: Core Authentication first, because the other feature sets depend on its session, user, role, and middleware work.
- Write each feature set, its owner, and any dependency in your Microsoft Teams channel so everyone can see the plan.
Agree on authentication conventions
- Agree what property will store the authenticated user on the request.
- Agree how protected API endpoints should return
401and403. - Agree which environment variables need to be configured locally and on Render.
- Agree how teammates will test signed-in and signed-out behavior.
Completion Checklist
- Every team member selected one feature set.
- The feature-set owners and dependencies were posted in Microsoft Teams.
- The team assigned and prioritized Feature Set 1: Core Authentication.
- The team agreed on basic authentication response and testing conventions.
Submission
When you are finished, return to Canvas to complete the team activity report or quiz.
Other Links:
- Return to: Week Overview | Course Home