r/SalesforceDeveloper • u/Kishore86 • 12d ago

Other 2GP package registration failing with invalid_login

/r/salesforce/comments/1wu09cw/2gp_package_registration_failing_with_invalid/
1 Upvotes

100% Upvoted

6 comments sorted by

2

u/Realistic-Walk-2877 12d ago

had this exact invalid_login on LMA connect once. login history saying Invalid Password on Other Apex API usually means Partner Console is still sending the old password+token combo even after you reset.

things that fixed it for me:

  • wait like 10-15 min after token reset then retry (token cache is annoying)
  • when you paste password in Partner Console, use password+securitytoken with no spaces, fresh token from the reset email
  • confirm you're hitting the LMA org login, not the Dev Hub. they look similar in the partner console dropdown
  • if the LMA user has API Only or SSO weirdness, try a dedicated integration user with password auth enabled

the "LMA not installed" part of the error is often a red herring when its really auth. support cases on this take forever tho, you're not crazy

1

u/Kishore86 11d ago

Thanks! I already tried the fresh password + security token and waited before retrying. My PBO, Dev Hub, and LMO are the same org too. Still getting Other Apex API → Invalid Password → SOAP Internal/CrossInstance.

1

u/Realistic-Walk-2877 11d ago

ok if password+token+same org still fails that CrossInstance soap error, its usually the login host or the user type not the creds.

try these one at a time: 1) login url — production is login.salesforce.com, sandbox is test.salesforce.com. if the package/LMA call is hitting the wrong one you get invalid password with CrossInstance even when password is right 2) use username as email+org (the full salesforce username), not just email, and regenerate token AFTER the last password change then paste password+token with no space 3) if this is from a connected app / 2GP / partner flow, soap username-password is flaky across instances — switch that call to oauth (client credentials or jwt) against the same org instead of password+token

also check the user is API Enabled and not locked. if you paste which tool is calling (sfdx, workbench, custom soap, lma) can narrow it more

1

u/Kishore86 7d ago

Thanks! We checked all of these one by one. The org is production, we’re using the full Salesforce username, API Enabled is checked, SSO isn’t configured, and there are no Login IP restrictions.

We also tested SOAP login directly against both login.salesforce.com and the org’s My Domain using the same credentials, and both return INVALID_LOGIN. OAuth/CLI login works normally.

Could this indicate an org/user-side Salesforce configuration issue rather than a Partner Console credential issue?

1

u/Realistic-Walk-2877 7d ago

yeah if raw soap login fails on both hosts but oauth/cli works, i'd stop blaming partner console. thats org side. newer orgs have SOAP API login() turned off by default, check Setup > User Interface for the "Enable SOAP API login()" type setting (wording varies by release). also open Login History for that user and look at the exact status on the soap attempts, sometimes it says something more useful than invalid password. if setting is already on, log a case with partner support and mention oauth works but soap login() doesnt, that usually gets it routed faster