Six authentication mistakes to fix are confused enrollment windows, reused backup codes, misused app passwords, kept revoked app passwords, overlong messages, and guessable repeated passwords.
Key takeaways for your staff login review
- Track the 45-day GitHub enrollment period and the 28-day checkup separately. The checkup starts only after 2FA is configured and ends on successful 2FA.
- Mark each Google backup code as used after entering it, because each 8-digit code can be used only once.
- App passwords work only with accounts that have 2-Step Verification turned on, and they are unnecessary in most cases.
- After any Google Account password change, expect app passwords to be revoked, and create a new one to keep an app working.
- Keep authentication messages shorter than 20 seconds, and use a password manager for long, random, unique passwords on every site.
Firm authentication mistakes: six documented errors to address
The first error involves confusing the two distinct authentication windows for GitHub. According to GitHub Docs, eligible groups receive a notification email marking the beginning of a 45-day 2FA enrollment period. After you configure 2FA, your account enters a checkup period for 28 days. You can leave the checkup period by successfully performing 2FA within those 28 days.
The second error is reusing Google backup codes. Google Account Help states that you click "Enter one of your 8-digit backup codes." As each code can be used only once, you might want to mark the code as used.
The third error involves misapplying app passwords. An app password is a 16-digit passcode that gives a less secure app or device permission to access your Google Account.
The fourth error is keeping revoked app passwords after a password change. The fifth error is using overlong authentication messages. The sixth error is choosing guessable repeated passwords.
At enrollment, distinguish GitHub's two authentication windows
Staff login reviews often conflate the initial enrollment window with the subsequent verification period. According to GitHub Docs, these are two distinct phases with different durations and exit conditions. Confusing them leads to incorrect tracking of staff compliance.
The first phase begins when a staff member in an eligible group receives a notification email. This email marks the start of a 45-day 2FA enrollment period, during which banners on GitHub.com prompt the user to enroll. The second phase starts only after the user has successfully configured 2FA. At that point, the account enters a checkup period lasting 28 days.
A common error is assuming the 28-day checkup period applies to everyone immediately after a policy announcement. It does not. It applies only after the user has configured 2FA. Furthermore, the checkup period is not a fixed duration that must elapse. A user can leave this 28-day period early by successfully performing 2FA within that timeframe. If a staff member completes a successful 2FA login on day three of the checkup period, the checkup ends. The review should track whether staff have completed the 45-day enrollment and whether they have performed a successful 2FA authentication to exit the 28-day checkup.
| Phase | Duration | Condition | Source |
|---|---|---|---|
| Enrollment | 45 days | Eligible group receives notification email | GitHub Docs |
| Checkup | 28 days | 2FA configured; ends on successful 2FA | GitHub Docs |
Record the date each staff member received their enrollment notification and the date they completed their first successful 2FA authentication. This allows you to verify that no one is stuck in an expired enrollment window or an unnecessarily prolonged checkup period.
Illustrative example: one staff member's dates
A staff member gets the notification on day 0, so the 45-day enrollment period runs to day 45. They configure 2FA on day 10, which starts the 28-day checkup. A successful 2FA sign-in on day 16 ends the checkup early.
At recovery, avoid reused codes and unsuitable app passwords
Recovery credentials follow strict usage rules that differ by format. Google Account Help defines backup codes as 8-digit entries used to sign in. Each of these codes can be used only once, so marking a code as used after entry prevents accidental reuse during a subsequent login attempt.
App passwords operate under different conditions. Google Account Help describes an app password as a 16-digit passcode that grants a less secure app or device permission to access a Google Account. These passcodes can only be used with accounts that have 2-Step Verification turned on. The documentation notes that app passwords aren't recommended and are unnecessary in most cases.
| Credential Type | Format | Usage Rule | Source |
|---|---|---|---|
| Backup code | 8-digit | Single use only | Google Account Help |
| App password | 16-digit | Requires 2-Step Verification | Google Account Help |
Ask each staff member whether they have entered any backup code more than once. Confirm whether 2-Step Verification is active before issuing any 16-digit app passwords.
After password changes, replace revoked app passwords
When a staff member changes the password for a firm-used Google Account, the existing app passwords for that account are revoked, according to Google Account Help. This automatic revocation applies to the specific account where the password change occurred. During a staff login review, confirm whether any recent password changes have interrupted app-based access to firm tools that rely on these credentials.
To continue using an app with the affected Google Account, create a new app password, as stated by Google Account Help. The previous app password remains invalid after the revocation event. Instruct staff to generate a replacement app password only for applications that require this specific sign-in method. Do not attempt to reuse the old app password, as it has been removed from the account.
Record the date of the password change and the date of the new app password creation in the firm's access log. This documentation helps verify that access was restored promptly after the revocation. Ensure that the new app password is stored securely and not written on paper or shared over unencrypted channels. The review should confirm that the staff member has successfully tested the new app password in the target application before closing the access issue.
At configuration, shorten messages and reconsider passwords
Configure authentication messages to stay under twenty seconds, as Microsoft Learn advises for Microsoft Entra multifactor authentication. Messages that exceed this twenty-second limit can cause the verification process to fail. When setting up these notifications for firm-used accounts, keep the message text concise to align with this documented technical constraint.
Beyond message length, address the risk of guessable passwords during your configuration review. The Cybersecurity and Infrastructure Security Agency notes that using an easy-to-guess password is like locking the door but leaving the key in the lock. To mitigate this, recommend that staff use a password manager, which makes it much more likely they will use a long, random and unique password on every site. When selecting a tool, read reviews to compare options and find a reputable program for your specific needs.
| Configuration Item | Limit or Recommendation | Consequence of Error | Source |
|---|---|---|---|
| Authentication message length | Shorter than 20 seconds | Verification can fail | Microsoft Learn |
| Password complexity and uniqueness | Long, random, and unique with a password manager | Easy-to-guess passwords leave security gaps | Cybersecurity and Infrastructure Security Agency |
Record which staff members have adopted unique, manager-generated passwords and confirm that all authentication messages meet the length requirement. Do not store the actual passwords or recovery codes in your review notes.
Authentication error reference table and review notes to retain
Use the following table as a checklist during your staff login review. Each row lists a specific authentication error, the documented condition or rule that defines it, and the publisher that documents the rule.
| Error Number | Specific Mistake | Documented Condition or Rule | Publisher |
|---|---|---|---|
| 1 | Confusing enrollment windows | 45-day enrollment period for eligible groups; 28-day checkup after configuration | GitHub Docs |
| 2 | Reusing backup codes | 8-digit codes are single-use | Google Account Help |
| 3 | Misapplying app passwords | 16-digit passcodes require 2-Step Verification; unnecessary in most cases | Google Account Help |
| 4 | Keeping revoked app passwords | App passwords are revoked when the Google Account password changes | Google Account Help |
| 5 | Using overlong authentication messages | Messages longer than 20 seconds can cause verification failure | Microsoft Learn |
| 6 | Choosing guessable repeated passwords | Easy-to-guess passwords compromise security; use unique passwords from managers | Cybersecurity and Infrastructure Security Agency |
Retain these notes for your review records. Record which account-specific conditions apply to your staff without recording passwords or recovery codes.
Enrollment distinctions The GitHub Docs source distinguishes two periods. The 45-day period begins when an eligible group receives a notification email. The 28-day checkup period begins after 2FA configuration. Successful 2FA within the 28 days ends the checkup.
Code and password hygiene Google Account Help states that 8-digit backup codes can be used only once. Google Account Help notes that 16-digit app passwords are unnecessary in most cases and are revoked when the account password changes. Create a new app password to continue using an app after a password change.
Configuration and password strength Microsoft Learn advises keeping authentication messages shorter than 20 seconds to avoid verification failure. Cybersecurity and Infrastructure Security Agency warns against easy-to-guess passwords and recommends using a password manager to maintain long, random, and unique passwords on every site. Read reviews to compare options and find a reputable program.
For handoffs inside the firm, see IRS contact authorization mistakes in firm handoffs and Accounting Client Intake Checklist for a Clear Handoff. Use the six documented errors as discussion points in today's staff login review and record which account-specific conditions apply without recording passwords or recovery codes.
Related guides: Payroll intake review against 4 source guides · Review 8 CP2000 details before sending client replies.
FAQ: staff login errors across supported account types
What firm authentication mistakes belong in a staff login review?
These six errors cover authentication conditions documented by GitHub, Google, Microsoft Entra, and CISA. Reviewing these points ensures staff understand the distinct rules for enrollment periods, code reuse, and message length limits.
Does the GitHub enrollment period apply if our staff received an enrollment notification?
Yes, if staff were in an eligible group, receiving a notification email marks the beginning of a 45-day 2FA enrollment period, as stated in GitHub Docs. During this window, users also see banners on GitHub.com asking them to enroll in 2FA. This period applies specifically to groups selected for enrollment by the platform.
Can a Google backup code be used more than once?
No, each 8-digit backup code is single-use, according to Google Account Help. Once a code is entered to sign in, it cannot be used again for future verifications.
When does changing a Google Account password revoke app passwords?
App passwords are revoked when the Google Account password is changed, according to Google Account Help. This revocation happens to help protect the account. If staff need continued app access after a password change, they must create a new app password.
How long should a Microsoft Entra authentication message be?
Authentication messages should be shorter than 20 seconds, as noted in Microsoft Learn. Messages longer than 20 seconds can cause the verification to fail. Keeping messages under 20 seconds is the documented guidance for avoiding verification failure.