Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(enterprise-connections/overview) remove info about pricing #1802

Merged
merged 3 commits into from
Dec 13, 2024
Merged

(enterprise-connections/overview) remove info about pricing #1802

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9611b65
(enterprise-connections/overview) remove info about pricing
alexisintech Dec 12, 2024
cebeb35
fix link
alexisintech Dec 12, 2024
14c7f83
put how much does it cost section back
alexisintech Dec 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 1 addition & 11 deletions docs/authentication/enterprise-connections/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ It is ultimately the app's responsibility to handle this unauthenticated state a

### SAML vs. EASIE

The primary security difference between EASIE SSO and SAML SSO is that EASIE depends on a multi-tenant identity provider, while SAML depends on a single-tenant identity provider. Relying on a multi-tenant provider **increases** the risk that a user from one tenant will mistakenly be granted access to the resources of another tenant. While Clerk implements [measures to address this risk](https://easie.dev/#mitigating-tenant-crossover-vulnerabilities), apps that require single-tenant IdPs should opt for SAML.
The primary security difference between EASIE SSO and SAML SSO is that EASIE depends on a multi-tenant identity provider, while SAML depends on a single-tenant identity provider. Relying on a multi-tenant provider **increases** the risk that a user from one tenant will mistakenly be granted access to the resources of another tenant. While Clerk implements [measures to address this risk](https://easie.dev/#mitigating-tenant-crossover-vulnerabilities:~:text=4.%20Mitigating%20tenant%20crossover%20vulnerabilities), apps that require single-tenant IdPs should opt for SAML.

For more information, see the [EASIE docs](https://easie.dev#security).

Expand All @@ -72,13 +72,3 @@ The users will not be deleted, so your app will not break. However, they will ne
### Does Clerk support IdP-initiated SSO?

Yes, for SAML only. Clerk supports both Service Provider-initiated (SP-initiated) and Identity Provider-initiated (IdP-initiated) SSO flows. For more information, see the [authentication flows guide](/docs/authentication/enterprise-connections/authentication-flows).

### How much does it cost?

For development instances, Enterprise connections are always free but limited to a maximum of 25.

Production instances require the Pro plan and the Enhanced Authentication Add-on. Please see [pricing](/pricing){{ target: '_blank' }} for more information.

### Can I get a bulk discount?

Yes, [contact support](/contact/support){{ target: '_blank' }} to work out a custom plan.
Comment on lines -82 to -84
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can delete the "Can I get a bulk discount?" section, but everything in the "How much does it cost?" section is still correct

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

put it back!! 14c7f83

Loading