public-offering
/
cal.pub0.org
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
cal.pub0.org/packages/features/ee
History
Carina Wollendorfer f6d7568d0a
Fixes formatted description in email (#7696) 
* fix description in email

* add styling for lists

* sanitize editor input before saving

* sanitize eventTypeDescription

* santize html when used dangerouslySetInnerHTML

* fix server side sanitation

* add missing formatting and sanitation

* move @ts-expect-error to correct line

* fix type error and add yarn.lock

* fix build error

* sanitize description for booking page and availability page

* rename to markdownAndSanitize

* always add list formatting

* handle empty description in markdownAndSanitize for cleaner code

* create function for clientside markdown rendering and sanitizing

* fix type error

* code clean up

* Now that eventType.descriptionAsSafeHTML is added at all the missing places, we can do away with ts-ignore and get type safety

* Remove unused variable

* Remove one more ts-expect-error

---------

Co-authored-by: CarinaWolli <wollencarina@gmail.com>
Co-authored-by: Hariom Balhara <hariombalhara@gmail.com>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
 		2023-03-23 12:00:42 +00:00
..
api-keys empty screen for unpublished teams (#7206) 2023-03-12 23:31:55 +00:00
common feat: create trpc route to fetch download link (#7495) 2023-03-05 12:59:07 +00:00
deployment/lib Admin Wizard Choose License (#6574) 2023-02-07 17:23:42 -07:00
impersonation feat(web): improve session retrieval performance (#7584) 2023-03-10 23:45:24 +00:00
payments Zomars/cal 884 paid events not sending the link (#7318) 2023-02-24 20:57:49 -07:00
sso refactor: event types kbar action (#7423) 2023-03-16 09:49:12 +00:00
support replacing intercom with helpscout (#7865) 2023-03-22 14:29:14 +00:00
teams Fixes formatted description in email (#7696) 2023-03-23 12:00:42 +00:00
video fix: use recordingId to check loading (#7524) 2023-03-06 10:39:54 +00:00
workflows Fixes additional inputs as variables in custom workflow templates (#7840) 2023-03-20 20:08:14 +01:00
LICENSE Refactors EE code (#3490) 2022-07-28 13:58:26 -06:00
README.md Update README.md 2023-02-12 20:33:16 +01:00
index.ts Refactors EE code (#3490) 2022-07-28 13:58:26 -06:00
package.json feat: adding custom field of type PHONE (#5623) 2022-12-16 12:39:41 -07:00

README.md

Enterprise Edition

Welcome to the Enterprise Edition ("/ee") of Cal.com.

The /ee subfolder is the place for all the Enterprise Edition features from our hosted plan and enterprise-grade features for Ultimate such as SSO, SAML, OIDC, SCIM, SIEM and much more or Platform plan to build a marketplace.

❗ WARNING: This repository is copyrighted (unlike our main repo). You are not allowed to use this code to host your own version of app.cal.com without obtaining a proper license first❗

Setting up Stripe

  1. Create a stripe account or use an existing one. For testing, you should use all stripe dashboard functions with the Test-Mode toggle in the top right activated.
  2. Open Stripe ApiKeys save the token starting with pk_... to NEXT_PUBLIC_STRIPE_PUBLIC_KEY and sk_... to STRIPE_PRIVATE_KEY in the .env file.
  3. Open Stripe Connect Settings and activate OAuth for Standard Accounts
  4. Add <CALENDSO URL>/api/integrations/stripepayment/callback as redirect URL.
  5. Copy your client*id (ca*...) to STRIPE_CLIENT_ID in the .env file.
  6. Open Stripe Webhooks and add <CALENDSO URL>/api/integrations/stripepayment/webhook as webhook for connected applications.
  7. Select all payment_intent events for the webhook.
  8. Copy the webhook secret (whsec_...) to STRIPE_WEBHOOK_SECRET in the .env file.

Setting up SAML login

  1. Set SAML_DATABASE_URL to a postgres database. Please use a different database than the main Cal instance since the migrations are separate for this database. For example postgresql://postgres:@localhost:5450/cal-saml
  2. Set SAML_ADMINS to a comma separated list of admin emails from where the SAML metadata can be uploaded and configured.
  3. Create a SAML application with your Identity Provider (IdP) using the instructions here - SAML Setup
  4. Remember to configure access to the IdP SAML app for all your users (who need access to Cal).
  5. You will need the XML metadata from your IdP later, so keep it accessible.
  6. Log in to one of the admin accounts configured in SAML_ADMINS and then navigate to Settings -> Security.
  7. You should see a SAML configuration section, copy and paste the XML metadata from step 5 and click on Save.
  8. Your provisioned users can now log into Cal using SAML.