Skip to main content

#Login Errors2 discutindo

Hello, 

 

The passkey for logging into my Salesforce-account isn't working (button doesn't react, in the correct browser) and the admin is also not able to create a temporary verification code (issue there as well?)... 

I tried creating a case for support, but that required logging in to the Salesforce-account... 

 

#Trailhead Challenges  #Login Errors

1 resposta
  1. Ontem 16:10

    The fix is the temporary verification code path — it bypasses the broken passkey entirely (log in with username and password, then enter the code at the MFA prompt). 

     

    Two things are likely blocking your admin: 

     

    1) The admin needs the Manage Multi-Factor Authentication in User Interface permission. Without it, the Generate option for a temporary code does not appear — that is usually why an admin cannot create one. Grant that permission via a permission set to any admin, then: Setup, Users, open the locked-out user record, click Generate next to Temporary Verification Code, and set an expiry (1 to 24 hours). 

     

    2) Once you are in with that code, disconnect the broken passkey on your user record and register a fresh MFA method. That same admin permission also lets them disconnect your passkey for you. 

     

    On the case catch-22: a Support case can be logged by any other admin in your org who can still log in — it does not have to come from your locked account. If literally no one can get in, that is the break-glass scenario and you would reach Salesforce Support through your org account contact. 

     

    if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

0/9000

I am the org admin and I created a test account to use in an environment we just set up, specifically for Salesforce iOS. However, every time I log in with the test account, I get the error pictured. It takes me through MFA, and the login is deemed successful on the admin side, but I am not actually able to access anything on the user side.

 

The app runs fine on my main account, so I'm not sure what the disconnect is. Does anyone have ideas on how to fix this (specific permissions that should be checked, or otherwise)?

 

#Salesforce For iOS/Android  #Login Errors  #Login Attempt  #Mobile  #Help

2 respostas
0/9000

I recognize/trust that Salesforce is working on fixing all of the organizations that have been disabled, but it's weird to me that there isn't any documentation online anywhere about this. I heard something similar may have happened in the recent past as well, so it seems it might be helpful to at least have something a person can find via a web search. (Salesforce's Status site doesn't even say anything!) #Login Errors #Error Message

4 respostas
0/9000

Hi everyone! Has anyone else experienced this issue? When I go to login, after I enter my password the loading screen freezes for a few seconds and then gives me a login error. What is odd is that I can see the Salesforce Authenticator app recognizing that I'm trying to login since I get an alert on the app, but I can't get passed the password page to enter my code. What is also odd is that I logged in fine this morning. Huge blocker that I can't get in to continue work...

 

I already created a ticket with Salesforce. This is a first for me but wanted to see if anyone else has experience this issue and if they have idea ideas on how to resolve.

 

Oh and I already tried on different browsers, cleared everything on my main browser (Chrome), tried on Safari, on my phone, etc. Nothing is working.

3 comentários
  1. 27 de abr. de 2021, 15:24

    Yep! Just saw the email regarding the PODs that are impacted:

    Impacted Instances:

    POD34, POD35, POD36, POD37, POD38, POD39, POD40, POD41, POD42, POD43, POD44, POD45, POD46, POD47, POD48, POD49, POD51, POD52, POD53, POD54, POD55, POD56, POD57, POD58, POD59, POD60, POD61, POD62, POD63, POD64, POD65, POD66, POD67, POD68, POD69, POD70, POD71, POD72, POD73, POD74, POD75, POD76, POD77, POD78, POD79, POD80, POD81, POD82, POD83, POD84, POD85, POD86, POD87, POD88, POD89, POD90, POD91, POD92, POD93, POD94, POD95, POD96, POD97, POD104, POD105, POD106, POD107, POD108, POD109, POD112, POD113, POD114, POD115, POD116, POD117, POD118, POD119, POD120, POD121, POD122, POD123, POD124, POD125, POD126, POD127, POD130, POD131, POD132, POD133, POD134, POD135, POD136, POD137, POD138, POD139, POD140, POD141, POD142, POD143, POD144, POD145, POD146, POD147, POD148, POD149, POD150, POD151, POD152, POD153, POD154, POD155, POD158, POD159, POD160, POD161, POD162, POD163, POD166, POD167, POD168, POD169, POD170, POD171, POD172, POD173, ,POD176, POD177, POD185, POD204, POD215

0/9000

Duplicate User - Self-Registration - Customer Service Template

 

We have an issue with Community Users attempting to self-register twice - it's going to happen, but the issue is the error message: the standard error message is Your request cannot be processed at this time. The site administrator has been alerted.  

 

Where can we change the wording on the error message to say "this username already exists, please go to the login page"?

 

Community is using the standard self-registration page in Community Builder,  Customer Service Template.

 

#Login Errors #Duplicate Users 

8 comentários
  1. 1 de abr. de 2019, 15:36
    Yes, apologies, I mentioned the wrong component/apex controller combination (was thinking of login messages for some reason!) - but @Frederic Banget is correct.
0/9000