Back to Blog
Grant Application Guide•October 19, 2026•10 min read

eRA Commons Login.gov Setup: Fixing Two-Factor Sign-In Problems

The eRA Commons login screen changed. Researchers who haven't completed the Login.gov transition will hit an authentication wall during their next submission — often within 48 hours of a deadline. Here's how the setup works and how to fix the most common problems before they cost you a cycle.

Why NIH Moved eRA Commons to Login.gov

In 2021, the federal government directed agencies to consolidate identity verification around a small number of approved credential service providers. Login.gov — operated by the General Services Administration — became the standard for civilian federal agencies. NIH began requiring eRA Commons users to link their accounts to Login.gov starting in 2022, with an expanding rollout by user role.

By 2026, nearly all eRA Commons users — principal investigators, key personnel, signing officials, and financial administrators — must authenticate through Login.gov before they can access any eRA module, including Commons, ASSIST, and the RPPR system. The old username-and-password flow with no mandatory second factor is now restricted to a narrow set of legacy configurations that NIH intends to phase out entirely.

The shift is a real security improvement. Login.gov enforces phishing-resistant two-factor authentication (2FA): you log in with a password plus a second factor — typically a TOTP authenticator app, a security key, or government-issued ID verification. What most researchers actually care about: if your institution hasn't already prompted you to complete the transition, do it before your next competing grant submission or RPPR, not during the 48-hour submission window when the eRA Service Desk queue is longest.

What You'll Need Before You Start

Before linking accounts, confirm three things are in order.

Your current eRA Commons credentials

Not a temporary password, not an expired one, and not something stored in your browser's autofill. You will have to type your eRA username and password manually during the linking process — the form does not accept autofill correctly. If you're unsure your password is current, reset it through the eRA Commons Forgot Password link first and confirm you can log in to eRA directly before starting.

A Login.gov account

If you don't have one, go to login.gov and create one. The Login.gov email doesn't have to match your eRA Commons email, though matching them reduces confusion. Many researchers use a personal Gmail precisely because institutional emails change between jobs and the Login.gov recovery process is tied to your registered address.

A second-factor device — plus a backup

Login.gov requires at least one authentication method beyond a password. An authenticator app (Google Authenticator, Microsoft Authenticator, or Authy) works on any smartphone and is the most practical choice. Set up a backup method — a second device or government-issued ID verification — at initial setup, not after you're already locked out.

One additional check: if your institution has a federated login (your university SSO appears on the eRA Commons login screen), contact your institutional research administration office before starting. Federated login has a different linking path, and the steps below may not apply directly.

Step-by-Step: Linking Your eRA Account to Login.gov

The linking process must be started from eRA Commons, not from login.gov. Going directly to login.gov takes you to your Login.gov account settings page — a dead end that many researchers mistake for an error. This is also one of the most common support calls the eRA Service Desk receives.

  1. Go to the eRA Commons login page (commons.era.nih.gov) and click "Link Your Account to Login.gov."
  2. Sign in to Login.gov when redirected. Use your Login.gov credentials here, not your eRA Commons password. Complete the 2FA step for your Login.gov account.
  3. Enter your eRA Commons credentials manually when you're returned to the eRA Commons linking screen. Type your eRA username and password by hand. Browser autofill often populates the wrong credentials or partially fills the form, which triggers an "invalid credentials" error even when the password is technically correct.
  4. Confirm the link. Once the credentials validate, eRA Commons links the two accounts and shows a confirmation screen. From this point forward, logging into any eRA module means clicking "Sign in with Login.gov" and completing your 2FA step.

If you see "This eRA Commons account is already associated with a Login.gov account" and you don't recall doing this, a previous colleague or institutional administrator may have initiated the process. Contact the eRA Service Desk — they can review and reset the association.

One thing that surprises most researchers: your eRA Commons password doesn't go away after linking. NIH still requires you to update it at least annually, even though you now sign in through Login.gov. Watch for the expiration prompt in your eRA-registered email inbox; an expired eRA password will block access even after you've successfully authenticated through Login.gov.

Common Login.gov Problems — and How to Fix Them

"Invalid eRA credentials" during linking

The single most common complaint. Almost always caused by browser autofill, an expired eRA password, or a temporary password set by your sponsored research administrator. Reset your eRA password through the Forgot Password link, confirm you can log in to eRA Commons directly, then restart the Login.gov linking process from the beginning. Do not try to debug the linking screen itself; the fix is almost always upstream.

Authentication failure or redirect loop

If Login.gov authenticates successfully but eRA Commons returns an error or sends you in circles, clear your browser's cookies and cache for the era.nih.gov domain and try again. Session artifacts from an earlier login can disrupt the OAuth handoff. Chrome and Firefox users should also disable extensions that intercept or modify redirects — some institutional VPN plugins trigger this behavior.

Lost access to your 2FA device

Log in at login.gov directly and go to "Manage your account." If you set up a backup authentication method during initial account creation, you can use it here to recover access. If you didn't, Login.gov's account recovery requires identity verification — plan on one to three business days. This is exactly the argument for adding a backup 2FA method at setup: a second authenticator device, or a government-issued ID linked to your account.

eRA Commons account locked out

eRA Commons locks accounts after a small number of consecutive failed logins — NIH documentation has cited thresholds ranging from three to five attempts. Lockout typically clears automatically after 15 minutes. Your institutional signing official or business official can also reset it from the Commons admin interface. For urgent situations before a deadline, the eRA Service Desk at 1-866-504-9552 can help during business hours.

The Multiple-Account Problem

Some researchers have more than one eRA Commons account — often because one was created during graduate training or a postdoc and a second was created upon starting a faculty position. NIH's guidance as of mid-2026 is to consolidate duplicate accounts before linking to Login.gov.

Login.gov allows only one eRA Commons account per Login.gov identity. If you try to link a second eRA account to the same Login.gov credential, you'll get an error. If you link different Login.gov accounts to each eRA account, you end up managing two separate Login.gov identities indefinitely — which creates confusion at every future submission and every RPPR.

The consolidation request goes to the eRA Service Desk. They'll ask you to identify the account you want to keep (typically the one tied to your current PI grants and most recent award history) and the one to deactivate. Submissions, training records, and credentials in the inactive account can generally be transferred. Make this request before any submission deadline — consolidation typically takes a few business days to process, and the timeline isn't adjustable for urgency.

Managing Your Credentials Going Forward

The Login.gov and eRA Commons combination gives you two sets of credentials to maintain: your Login.gov password and your eRA Commons password. They're separate, and both need to stay current.

Set a calendar reminder to check your eRA password before each submission cycle. NIH sends expiration notices to the email address registered in eRA Commons — which may not be your current primary inbox if you've changed institutions since you first created the account. An expired eRA password is one of the most common reasons researchers can't access ASSIST in the week before a deadline, and it's not obvious that this is the problem when Login.gov authentication itself succeeds.

Login.gov passwords don't expire on a forced annual cycle, but Login.gov does deactivate dormant accounts. If you've had a gap in grant activity — a sabbatical, a postdoc-to-faculty transition, extended fieldwork — log into login.gov at least once before your next eRA session to confirm the account is still active. If your institution migrates or updates its SSO system, the federated login path may change; your research administration office will communicate this, and those emails are worth reading before the next submission cycle begins.

Frequently Asked Questions

Do I need Login.gov to use NIH ASSIST?

Yes. ASSIST is an eRA module, and all eRA modules now require Login.gov authentication for users subject to the 2FA requirement. The deadline is 45 days after you submit a competing grant application (Type 1 or Type 2) or an RPPR. Don't wait for that clock to start — set up Login.gov now, before your next submission, not during the 48-hour window.

Can I use a personal email for Login.gov?

Yes. Login.gov doesn't require an institutional email address. Many researchers use a personal address specifically because institutional emails change between jobs and institutions. If you use a personal email, your institution's IT help desk won't be able to help with Login.gov account recovery — that goes through login.gov's own identity verification process.

What if my institution uses federated login?

Institutions with NIH SSO configured have a different login path. You'll see your institution listed on the eRA Commons login screen. The Login.gov linking steps above may not apply directly — contact your sponsored research office before starting to confirm which process your institution uses and whether your IT team handles any part of it.

Does the 2FA requirement apply to trainees and fellows?

Yes. Fellowship applicants — F31, F32, K99/R00, and others — who have their own eRA Commons accounts are subject to the same 45-day deadline as PIs. Trainees setting up their first eRA account should complete the Login.gov link before their first submission, not as an afterthought after the application PDF has already gone to their institution for sign-off.

Know Your Funding Landscape Before You Submit

Getting into eRA Commons is the first step. Understanding what to submit, to which institute, and at what time makes the difference between a competitive application and one that misses the mark.

Trust & Transparency

How this content is reviewed before it goes live

NIH Grant Explorer combines public NIH records with editorial interpretation. We publish the review structure, methodology, and correction pathways so readers can judge the value of a guide or chart for themselves.

When a topic turns into an official policy question, we point readers back to NIH rather than pretending an independent site can replace the underlying federal guidance.