Search Results :×
miniOrange HubSpot OAuth Single Sign-On (SSO) application enables secure login into HubSpot CMS landing pages, blogs and other pages using LinkedIn as OAuth provider. It supports advanced Single Sign-On (SSO) features such as user profile Attribute mapping, etc.
Here we will go through a guide to configure SSO between HubSpot and LinkedIn. By the end of this guide, users should be able to login to HubSpot from LinkedIn. To know more about miniOrange HubSpot OAuth Single Sign-On plugin and other HubSpot Integrations, you can click here.
Feel free to contact us at firstname.lastname@example.org to know more about how to install the miniOrange HubSpot OAuth Single Sign-On app.
|Client ID :||from the step 1 above|
|Client Secret :||from the step 1 above|
|Header / Body Setting||Enable the Send in Body parameter option|
|Access Token Endpoint:||https://www.linkedin.com/oauth/v2/accessToken|
|Get User Info Endpoint:||https://api.linkedin.com/v2/me|
Restricting access to your HubSpot website can help to protect your pages from unauthorized access. By restricting access, you can ensure that only authorized users can view and interact with your pages. This can be useful for protecting sensitive information. This will allow you to restrict access to your HubSpot pages / content as visitors will be needed to login first and then they will be able to access the HubSpot page. This will also help you to track your vistors and also generate potential leads.
There are a couple of reasons why this can happen:
1. Caching is enabled on the website.
When auto-redirect is enabled, the user is redirected to IDP login page and after logging in back to the main site but as caching is enables it redirects to the IDP login page hence a loop.
2. HTTP/HTTPS discrepancy:
This happens when HTTPS is not enforced on the site but is configured on IDP side with HTTPS URL.This can be solved by enforcing HTTPS on the site by defining a redirect rule in the .htaccess file or at the Apache level.
3. Cookie adulteration:
The cookie created by the plugin after logging in the user is altered by another plugin which causes the user to not log in WordPress site but the session is created on IDP.
There can be 2 possibilities:
To fix this issue, please configure the correct Token and User info endpoint in the HubSpot SSO application endpoint table. You can confirm the correct format of the endponit from HERE.
Mail us on email@example.com for quick guidance(via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.
Need Help? We are right here!
Thanks for your inquiry.
If you dont hear from us within 24 hours, please feel free to send a follow up email to firstname.lastname@example.org
Necessary cookies help make a website fully usable by enabling the basic functions like site navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any personal identifiable information. However, some parts of the website will not work properly without the cookies.
These cookies only collect aggregated information about the traffic of the website including - visitors, sources, page clicks and views, etc. This allows us to know more about our most and least popular pages along with users' interaction on the actionable elements and hence letting us improve the performance of our website as well as our services.