I manage a small business. We’re not going to be even considering Enterprise Tier for the foreseeable future due to our size and needs.
I challenge HubSpot to make this available for all product tiers.
SSO enables much better security. There is a case that small businesses need more protection against security issues than any other buyer type, and that HubSpot cares for the security for all customers equally. It feels like a crummy item to use as an upsell tactic.
+1 Upvote
@Bracken & @AQT_MKr I have the product you might be looking you for - Single Sign-On which supports all-tier. Currently, it works with CMS websites and page protection. It would be great to hear from you about the SSO feature set you are interested. Can you please share your SSO requirements?
You can also test the solution here: hubapps.miniorange
Hi All
I am a Product Manager in HubSpot and doing research on our customer needs for SAML-based SSO. I appreciate your feedback on the topic of Single Sign-on.
In HubSpot, we do offer social logins like Login with Google and Microsoft for all tiers. I am wondering why this will not work for you?
Why do you need to use SAML SSO in other tiers? Please let us know the reason:
1. It is the enterprise standard for SSO and you have other applications connecting using the same SAML protocol. You have a working SSO architecture laid down using SCIM based user provisioning and SAML SSO authentication with appropiate relayState and don’t want to deviate from the standard model.
2. You have a mix of on-prem, legacy and cloud applications which necessities SAML as OIDC will not work for on-prem and legacy applications
3. Your current IdP may only support SAML for SSO (e.g. older version of Microsoft ADFS) or your IdP only provides SSO based application connectors
4. You want your users to connect to a specific IdP instance for your company’s specific business domains
5. You have external users/contractors whose email may not be that of Google or Microsoft. In this case they cannot use Login with Google or Login with Microsoft
6. Today, you cannot explicitly specify what social login providers are trusted in their portals. There will be issues in enforcement as a user from social login may have identity with different policies. These issues can only be solved using SAML SSO integration.
7. Any other reason?
Thanks,
Kaushik