As an alternative to logging in with your LeadSquared credentials, you can configure your account to enable log-in through the following third-party authentication providers –
- Active Directory Federation Services (ADFS)
- API
This article contains instructions on setting up Google or API as your authentication provider. For instructions on ADFS, see ADFS Integration for Sign-in in LeadSquared.
Prerequisites
- Only LeadSquared admins can configure the authentication provider for an account.
- To make Google your authentication provider, your Google Id and LeadSquared email Id must be the same.
- The API is not available by default. Contact us at support@leadsquared.com to enable it for your account. Also,
- Your user id/email address in the third-party application must be the same as your LeadSquared email Id.
- You must expose an API URL that is accessible over the internet.
Authentication Provider Settings
- Navigate to My Profile>Settings>Security>Authentication Provider.
- Click the slider
alongside Enable Third Party Authentication Provider.
Here’s how to use Google as your authentication provider and log-in to LeadSquared with your Google credentials –
1. Once you enable the third party authentication provider setting, on the Choose Authentication provider pop-up, click Google.
2. Click the Sign-in with Google button, then enter your Google credentials and sign-in.
3. From this point on, you’ll be prompted to enter your Google credentials on logging-in to LeadSquared.
API
You can use the credentials of a third-party tool to log in to LeadSquared. Ensure that the user/email Id in the tool is the same as the LeadSquared email Id. Expose an API that is accessible over the internet and use the settings below to configure what data you want to pass.
After enabling the third party authentication provider setting, on the Choose Authentication provider pop-up, click API.
On the Configure Authentication Provider pop-up, enter the details of the API you’ve exposed. When you’re done, click Test.
Field | Description |
Request Type | Choose HTTP request method as either GET or POST. |
API URL | Select either http:// or https:// and enter your API URL here. Type @ to use mail merge fields in the query string. |
Content Type | Currently, data can only be sent as application/json. |
Request Headers | You can pass multiple request headers here. |
Request Body | If you select the Request Type as POST, you can enter a valid json in the request body. Type @ to make use of mail merge fields |
Success Keyword | This is the success keyword that should be present in a successful response. |
Error Keyword | The error keyword that should be present in the error response. |
Note: To send passwords, you must type the mail merge field @{User:Password ,}. For IP address, you must enter @{User:ClientIP ,}. These fields will not show up in the mail merge dropdown that appears when you type @.
Now enter your credentials, and click Enable.
Any Questions?
If you have questions, go ahead and start a discussion in the comments section below. We’ll get back to you ASAP!
If third party authentication is turned on, do users get a choice to use it or not? And, can it be bypassed (i.e., is there a direct link that will bypass SSO?).
Hi, Nathan. Thanks for writing to us. Once enabled, we do not support the option to bypass third-party authentication. There’s no direct link to bypass third-party authentication either. It becomes mandatory for all users in your organization. Hope this helps!