Participant Auto Authentication
If your campaign is configured to have participants login/authenticate, you can set up Participant Auto Authentication to automatically log participants into their browser.
Last updated
If your campaign is configured to have participants login/authenticate, you can set up Participant Auto Authentication to automatically log participants into their browser.
Last updated
Step 1: Require participants to login/authenticate within the Campaign Editor
Step 2: Generate a new Participant Auth Secret
Step 3: Copy your unique Participant Auth Secret (to use for later in the Setting up the server instructions).
Your Participant Auth Secret holds privileges, so be sure to keep it secure! Do not share your Participant Auth Secret in publicly accessible areas such as GitHub, Bitbucket, client code, etc.
Step 4: Go to the final instructions page within the Campaign Editor to copy the new GrowSurf Universal Code.
Once your campaign has a Participant Auth Secret, the installation instructions will be updated and you will need to re-install a newly generated GrowSurf Universal Code snippet.
This new GrowSurf Universal Code snippet contains a new window.grsfConfig
Object. Remember to replace two values: (1) set email
as the participant's email address, and (2) set hash
as the value you receive from setting up the server. See the example code block below:
On your server, you will need to create a Hash-based message authentication code (HMAC).
Step 1: Implement SHA-256 HMAC, passing in the following values:
The Participant Auth Secret (from Step 3 of the Setting up the client section)
The participant's email address
Below is an example of the HMAC implementation in Node.js:
Test your Participant Auto Authentication implementation by going to the URL in which you have installed GrowSurf.
Then load or refresh the page. If successful, you should be authenticated as a participant.
Below are additional references that may be helpful:
JavaScript Web API method growsurf.init()