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
Hariom Balhara c2996cd2f8
fix: 404 booking pages when org support is enabled locally 
## What does this PR do?
Fix 404 booking pages when org support is enabled locally

## Type of change

<!-- Please delete bullets that are not relevant. -->

- Bug fix (non-breaking change which fixes an issue)

## How should this be tested?

<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -->

-  Add localhost:3000 to ALLOWED_HOSTNAMES which is the default recommendation for enabling org support locally.
<img width="1035" alt="Screenshot 2023-07-10 at 11 04 35 AM" src="https://github.com/calcom/cal.com/assets/1780212/7272437b-afae-4073-905b-eafc39f9fafc">
- Simply restart the server and visit http://localhost:3000/pro. It will give 404. After this change it would work

## Mandatory Tasks

- [x] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.
 		2023-07-10 12:19:33 -07:00
..
api-keys feat: org invite billing (#9291) 2023-07-02 11:40:12 -07:00
common refactor: Skip license checks for development (#9375) 2023-06-21 23:13:26 -03:00
components CAL-1589: Added utm link to powered by in booker. Also added new colors to powered by component, so theyre also used in current booker form now on. (#8670) 2023-05-05 08:36:23 +01:00
deployment/lib Admin Wizard Choose License (#6574) 2023-02-07 17:23:42 -07:00
impersonation test: Adds permission tests to impersonation (#9660) 2023-06-20 13:42:37 +00:00
managed-event-types feat: Enable Apps for Teams & Orgs [CAL-1782] (#9337) 2023-07-06 16:48:39 +00:00
organizations fix: 404 booking pages when org support is enabled locally 2023-07-10 12:19:33 -07:00
payments fix: cancel button not working on payment page (#10006) 2023-07-10 15:58:38 +02:00
sso feat: org invite billing (#9291) 2023-07-02 11:40:12 -07:00
support fix: user undefined (#9022) 2023-05-22 23:02:54 +00:00
teams chore: Teams empty screen (#9997) 2023-07-10 10:44:22 -04:00
users feat: temp admin user management 2023-07-07 18:25:21 +05:30
video fix: upgrade btn bug (#9104) 2023-05-29 20:31:55 -07:00
workflows feat: org invite billing (#9291) 2023-07-02 11:40:12 -07:00
LICENSE Update LICENSE 2023-05-22 18:56:17 +01: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 change /ee to /commercial (#8948) 2023-05-25 17:50:30 +00: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.