AUTHENTICATE.COM ======================

DESCRIPTION
------------------------
 AUTHENTICATE.COM allows Knowledge Based Authentication, Photo ID & Passport Verification, Age, Employment, Education & Criminal Background Checks, MVR & DMV Records, Email, SMS, FEIN & SSN Verification.

 The flow starts by creating a unique authentication URL from the user attributes (email, names, date of birth, etc). Once the verification is complete, AUTHENTICATE.COM sends the USER ACCESS CODE via WEBHOOK to your app. You must then query the VERIFICATION RESULTS using this USER ACCESS CODE.
Finally, you may save the VERIFICATION RESULTS to the correct user by matching the user's email address contained in those VERIFICATION RESULTS.

STEP-BY-STEP SETUP
--------------------------------
 0) Create and activate an account on AUTHENTICATE.COM.

 1) a) Set in your PLUGIN SETTINGS your COMPANY ACCESS CODE, available after account activation. The COMPANY ACCESS CODE is set as Public key as it is required to generate the unique URL for a given user from the element, contrary to your API Key which remains secret.

 1) b) Set in your API KEY prefixed by "Bearer ".

 2) Add the AUTHENTICATE.COM element on the page on which you wish to implement user authentication.

 3) Make sure the element is visible.

 4) Create a page to which the user will be redirected to after the verification is complete. Typically you may want to show the VERIFICATION RESULTS on that page.

 5) In a workflow triggered by a button for example, add the GENERATE AUTHENTICATION URL action and set the following fields:

 FIELDS :
 - FIRST NAME : First Name to match against the verification method.
 - MIDDLE NAME : Middle Name to match against the verification method.
 - LAST NAME : Last Name to match against the verification method.
 - DATE OF BIRTH : Date of Birth to match against the verification method.
 - EMAIL : Email of the user to be authenticated.
 - VERIFICATION OPTIONS : EITHER: Lets the user Upload their ID/Passport or answer the Identity Proof Quiz | BOTH: Asks the user to mandatorily Upload their ID/Passport and answer the Identity Proof Quiz | DOCUMENT_ONLY: Upload ID/Passport Only | QUIZ_ONLY: Identity Proof Quiz only
 - REDIRECT URL : Redirect URL has to be a valid SSL Secured URL. Typically this URL is a Bubble page displaying the verification results to your user.

 6) Add a new workflow with the triggering event being AUTHENTICATION URL GENERATED. This event fires once the element has generated the unique authentication URL your user will be directed to.

 7) Create a USER ACCESS CODE field (or create the fields containing desired VERIFICATION RESULT data) in the User table of your app.

 8) Use the action "OPEN AN EXTERNAL WEBSITE" to open the URL in the AUTHENTICATION URL of the element. You should now be able to trigger a first authentication request, to be done at step 14.

 10) Now we must create the endpoint from which the USER ACCESS CODE will be received from AUTHENTICATE.COM after the user has completed the verification.
 Go to your APP > BACKEND WORKFLOWS, create a NEW API WORKFLOW, check the options "EXPOSE AS A PUBLIC API WORKFLOW", "THIS WORKFLOW CAN BE RUN WITHOUT AUTHENTICATION", "IGNORE PRIVACY RULES WHEN RUNNING THE WORKFLOW". Set the first action as "RETURN DATA FROM API", "PLAIN TEXT", value "OK.

 11) In "PARAMETERS DEFINITION", set the option to "DETECT REQUEST DATA".

 12) Click on "DETECT DATA", copy the URL.

 13) Go to your AUTHENTICATE.COM USER PORTAL > SETTINGS > WEBHOOK, paste the URL.

 14) Perform a verification by clicking on the button set up earlier in order to send data to the webhook to initialize it.

 15) After the verification is complete, you will notice that the previously created API WORKFLOW has detected incoming data containing the USER ACCESS CODE.

 16) Go back to your AUTHENTICATION.COM USER PORTAL > SETTINGS > WEBHOOK and remove the /initialize part of your WEBHOOK URL.

 17) Finalize the API WORKFLOW you started to implement at step 10 by using the action GET DATA FROM AN EXTERNAL API "AUTHENTICATE.COM - GET TEST RESULTS".

   Inputs Fields :
     - USER ACCESS CODE : USER ACCESS CODE contained in the WEBHOOK payload after the verification has completed.

   Output Fields : VERIFICATION RESULT containing also the user attributes.

 18) At this stage, you may want to save the USER ACCESS CODE (or the desired authentication data) into the User field created at step 7, the user being matched with its email address contained in the response.

 19) Finalize the redirect page created at step 4 by displaying the result of the verification, typically by displaying the VERIFICATION RESULT based on the data stored at the step 18, depending on your implementation.

 20) Remember that the webhook URL contains your branch version (/version-test/ for example). Amend the webhook URL in AUTHENTICATE.COM portal according to the branch you are working on.

IMPLEMENTATION EXAMPLE
======================
Feel free to browse the app editor in the Service URL for an implementation example.

TROUBLESHOOTING
================
Any plugin related error will be posted to the the Logs tab, "Server logs" section of your App Editor.
Make sure that "Plugin server side output" and "Plugin server side output" is selected in "Show Advanced".

> Server Logs Details: https://manual.bubble.io/core-resources/bubbles-interface/logs-tab#server-logs

PERFORMANCE CONSIDERATIONS
===========================
 N/A

QUESTIONS ?
===========
Contact us at [email protected] for any additional feature you would require or support question.