528
edits
Login Component: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 53: | Line 53: | ||
== Session Key == | == Session Key == | ||
The login component generates a sessionKey, a hashed cookie-like string that sticks to the user's browser and has a set expiration date. The Login Component has the ability to check the validity of the sessionKey, and through Apex, developers can also use the sessionKey to extract the contact Id of the logged in user: <code>RemoteUtils.getContextUserContactId(String sessionkey);</code> | The login component generates a sessionKey, a hashed cookie-like string that sticks to the user's browser and has a set expiration date. The Login Component has the ability to check the validity of the sessionKey, and through Apex, developers can also use the sessionKey to extract the contact Id of the logged in user: <code>RemoteUtils.getContextUserContactId(String sessionkey);</code> | ||
== Login, Register and Reset Password == | |||
The login component allows user login, by using a Contacts for authentication. Here's a map of the fields involved in the authentication: | |||
- Username is the Contact.Email | |||
- Password is the Contact.b3o__Password__c, | |||
- Veri Code (verification code) is the Contact.b3o__Temporary_Password__c | |||
'''''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.''''' | |||
== Conclusion == | == Conclusion == | ||