OAuth 2 FAQ

What does the flow look like from the Advocate point of view?

Using OAuth 2 Single Sign On

The flow for the advocate is as follows:
  1. Navigate to the AdvocateHub URL
  2. They will be immediately be redirected to the login screen you have configured as your login point for your Advocates
  3. Advocate enters the AdvocateHub

Note: If an advocate is already a member of another AdvocateHub with the same email address then there is one additional step in the flow. After they successfully enter their credentials into the customer portal, they will see a message like below:

An email will be sent to the Advocate which will include a link which they just have to click on and they will be brought back to the login screen to enter their credentials once more before gaining access to the AdvocateHub.

Here is a visual walkthrough of the flow the Advocate will experience:


Using OAuth Dual Login

The flow for the advocate is as follows:

  1. Navigate to the AdvocateHub URL
  2. They will be brought to the AdvocateHub Sign In page. They will be greeted with the opportunity to login through the Single Sign-On or click Click here to Sign In to reveal the regular login form where they can enter their email & password and access the Advocatehub:

Do Join URL/Codes work with OAuth 2?

Yes. You can use these exactly as you would normally expect with the AdvocateHub. Read more on join URLs here

How do invites work with OAuth 2?

Important Note about Nominees and SSO 

If you have a Nominee in your AdvocateHub and then this user tries to sign up to the AdvocateHub using a join URL or by navigating directly to the AdvocateHub they will experience permissions issues. Currently, the only way to 'upgrade' a Nominee to an Advocate is by sending them an invite directly from AdvocateHub, they will then need to click the link contained in the invitation to gain access to the AdvocateHub as an Advocate.

To study some other options on how you can segment your Advocates check out  this article.

Things to think about if implementing OAuth 2 on an active Hub

If your hub is already up and running and has many Advocates already joined up this could cause some issues if you choose to enable OAuth Single Sign-On, these obstacles can be overcome with some preparation and thought.
Let's take this example, if I have signed up to your AdvocateHub using the email address sean@gmail.com but the email address I use to sign in to your product or portal is sean@influitive.com.

In this case I try to access the hub and am directed to your product or platform to complete the login process. I enter sean@influitive.com and my password and enter the hub successfully but now I will have a brand new account setup as the AdvocateHub did not have an email address sean@influitive.com present, it was looking for sean@gmail.com.

What can you do to prepare for this?

We recommend coming up with a strategy of sending communications to your Advocates notifying them of this changeover and letting them know they have to update their email address to match whatever email address they use to access your product or platform. You can do this through email blasts or with a challenge or a combination ideally to try and catch as many people as possible. If Advocate's fall through the cracks we can fix this up for you by merging the duplicate accounts including points and badges but this may take some time to do.
Another method you could use to preempt this issue is to gather all the email addresses of your Advocates in the AdvocateHub and then check them against the email addresses in your database. If there is no match for an email address then you can create an account in your database with this email address. This way the person can continue to use the email address they have been using in the AdvocateHub and no duplicate Advocate accounts will be created.

Can I have some Advocates use OAuth 2 SSO but others to use the traditional method of login?

Yes. With OAuth 2 you can choose to enable Dual Sign-On, this allows your Advocates to choose whether to login through Single Sign-On or using the traditional email/password method. This may be helpful if you have Employees and Customers in your program and you would like your employees to use Single Sign into login but your customer to use their email and password.

This is what will greet the Advocate when they navigate to your AdvocateHub if you have Dual Sign-On enabled:

In order to find out how you can switch between Single Sign-On and Dual Sign On have a look at our Configuring OAuth 2 article.

Where are the 'Terms and Conditions' housed when using OAuth 2?

You can set the Terms & Conditions under Settings > Advocate Program > Sign-In. Simply enter your desired Terms & Conditions and toggle 'on'.

Using OAuth 2 Single Sign-On
As we completely bypass the AdvocateHub in this case, there is no place for the Advocate to agree to terms and conditions before they login. They can find them once they login by clicking on their avatar and selecting Terms and Conditions from the drop-down menu

Using OAuth Dual Login
This time when the Advocate chooses to sign up with the traditional email/password method, they see the terms and conditions linked at the bottom of their sign up form and they then must check the box here to accept these terms and conditions

How does the Maven app work with OAuth 2?

The process is as seamless on the Maven app as it is on your desktop. Let us have a look at the flow when logging in to an SSO enabled AdvocateHub;
1. Opening the Maven app, you will be greeted with a screen like below. The advocate can hit any of the social sign-in buttons in order to access the AdvocateHub as long as they have associated any of them previously with their advocate profile. They will be instantly brought to a list of the AdvocateHubs they have access to. The advocate can also enter the email address associated with their AdvocateHub account and hit Continue which will take them to another screen before they can see their list of AdvocateHubs.
2. If the advocate has no social authentications tied to their account and have entered their email address then they should see this option below, here they will have to send a sign in link to their email address. They should instantly receive an email with a link that they will need to follow.
3. Once they follow the link they receive they will be brought back into the Maven app and will see a list of the AdvocateHubs they have access to.
4. Finally, they click on the AdvocateHub they want to enter and voilá!

Still need help? Contact Us Contact Us