528
edits
Login Component: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 64: | Line 64: | ||
'''''Note, that when the user requests password reset, the field b3o__Temporary_Password__c is set to a numerical value. The implementation team/developers would need to create a Flow/Automation to send an email to the Candidate with the value from that field. Each un-successful attempt to verify the veri-code will issue a new veri-code, so a new email should be sent.''''' | '''''Note, that when the user requests password reset, the field b3o__Temporary_Password__c is set to a numerical value. The implementation team/developers would need to create a Flow/Automation to send an email to the Candidate with the value from that field. Each un-successful attempt to verify the veri-code will issue a new veri-code, so a new email should be sent.''''' | ||
== Error Messages == | |||
{| class="wikitable" | |||
|+ | |||
!Name | |||
!Label | |||
!Meaning | |||
!Action | |||
|- | |||
|Auth_WrongPassword | |||
|Invalid or wrong password. | |||
|Contact's password is blank or the request sent a blank password | |||
|Make sure that the contact has a password set in the b3p__Password__c field. If the issue persists even after ensuring that there is a password, contact 3B Support | |||
|- | |||
|Auth_InvalidUsername | |||
|Looks like you are not registered | |||
|We didn't find any contacts in the system with the requested email or the request to the server was made without a username | |||
|Make sure that the contact has an Email set in the Email field. If the issue persists even after ensuring that there is a password, contact 3B Support | |||
|- | |||
|Auth_InvalidUsernamePassword | |||
|Invalid username or password | |||
|The password entered by the user was incorrect | |||
|User needs to reset password | |||
|- | |||
|DMLException | |||
|An error displayed when user attempts to reset their password | |||
|When a user attempts to reset their password, we are setting the veri code to the b3p__Temporary_Password__c field. Validation rules or failing automations could prevent this. | |||
|Check for validation rules, flows, apex code or other automations that may prevent the user's contact from being updated. | |||
|- | |||
|Portal_InvalidTempPass | |||
|The provided verification code is invalid. Try again. | |||
|The user has entered a verification code that is invalid or old. The b3p__Temporary_Password__c field will be updated with a new verification code and the user can try again. | |||
|User needs to enter a valid verification code. | |||
|} | |||
== Pre-populating the Login Form == | |||
You can pre-populate the fields on the login form by passing URL parameters to the Portal page that requires user login (only works if the user is not logged in already). Here are the parameters and their possible values: | |||
* frontDoor - you can pass: register | resetPass | confirmPassReset | login (default) | |||
* username - the user's email | |||
* vericode - the verification code | |||
So, to make it easier for user re-setting their password, you can forward them to a url that looks like this: | |||
https://company.salesforce.com/onboarding#Page<nowiki/>?frontDoor=confirmPassReset&username=test@email.com&vericode=1234 | |||
== Conclusion == | == Conclusion == | ||