
* Add log in with Google * Fix merge conflicts * Merge branch 'main' into feature/copy-add-identity-provider # Conflicts: # pages/api/auth/[...nextauth].tsx # pages/api/auth/forgot-password.ts # pages/settings/security.tsx # prisma/schema.prisma # public/static/locales/en/common.json * WIP: SAML login * fixed login * fixed verified_email check for Google * tweaks to padding * added BoxyHQ SAML service to local docker-compose * identityProvider is missing from the select clause * user may be undefined * fix for yarn build * Added SAML configuration to Settings -> Security page * UI tweaks * get saml login flag from the server * UI tweaks * moved SAMLConfiguration to a component in ee * updated saml migration date * fixed merge conflict * fixed merge conflict * lint fixes * check-types fixes * check-types fixes * fixed type errors * updated docker image for SAML Jackson * added api keys config * added default values for SAML_TENANT_ID and SAML_PRODUCT_ID * - move all env vars related to saml into a separate file for easy access - added SAML_ADMINS comma separated list of emails that will be able to configure the SAML metadata * cleanup after merging main * revert mistake during merge * revert mistake during merge * set info text to indicate SAML has been configured. * tweaks to text * tweaks to text * i18n text * i18n text * tweak * use a separate db for saml to avoid Prisma schema being out of sync * use separate docker-compose file for saml * padding tweak * Prepare for implementing SAML login for the hosted solution * WIP: Support for SAML in the hosted solution * teams view has changed, adjusting saml changes accordingly * enabled SAML only for PRO plan * if user was invited and signs in via saml/google then update the user record * WIP: embed saml lib * 302 instead of 307 * no separate docker-compose file for saml * - ogs cleanup - type fixes * fixed types for jackson * cleaned up cors, not needed by the oauth flow * updated jackson to support encryption at rest * updated saml-jackson lib * allow only the required http methods * fixed issue with latest merge with main * - Added instructions for deploying SAML support - Tweaked SAML audience identifier * fixed check for hosted Cal instance * Added a new route to initiate Google and SAML login flows * updated saml-jackson lib (node engine version is now 14.x or above) * moved SAML instructions from Google Docs to a docs file * moved randomString to lib * comment SAML_DATABASE_URL and SAML_ADMINS in .env.example so that default is SAML off. * fixed path to randomString * updated @boxyhq/saml-jackson to v0.3.0 * fixed TS errors * tweaked SAML config UI * fixed types * added e2e test for Google login * setup secrets for Google login test * test for OAuth login buttons (Google and SAML) * enabled saml for the test * added test for SAML config UI * fixed nextauth import * use pkce flow * tweaked NextAuth config for saml * updated saml-jackson * added ability to delete SAML configuration * SAML variables explainers and refactoring * Prevents constant collision * Var name changes * Env explainers * better validation for email Co-authored-by: Omar López <zomars@me.com> * enabled GOOGLE_API_CREDENTIALS in e2e tests (Github Actions secret) * cleanup (will create an issue to handle forgot password for Google and SAML identities) Co-authored-by: Chris <76668588+bytesbuffer@users.noreply.github.com> Co-authored-by: Omar López <zomars@me.com>
84 lines
3 KiB
Text
84 lines
3 KiB
Text
# Set this value to 'agree' to accept our license:
|
|
# LICENSE: https://github.com/calendso/calendso/blob/main/LICENSE
|
|
#
|
|
# Summary of terms:
|
|
# - The codebase has to stay open source, whether it was modified or not
|
|
# - You can not repackage or sell the codebase
|
|
# - Acquire a commercial license to remove these terms by emailing: license@cal.com
|
|
NEXT_PUBLIC_LICENSE_CONSENT=''
|
|
|
|
# DATABASE_URL='postgresql://<user>:<pass>@<db-host>:<db-port>/<db-name>'
|
|
DATABASE_URL="postgresql://postgres:@localhost:5450/calendso"
|
|
|
|
# Needed to enable Google Calendar integrationa and Login with Google
|
|
# @see https://github.com/calendso/calendso#obtaining-the-google-api-credentials
|
|
GOOGLE_API_CREDENTIALS='{}'
|
|
|
|
# To enable Login with Google you need to:
|
|
# 1. Set `GOOGLE_API_CREDENTIALS` above
|
|
# 2. Set `GOOGLE_LOGIN_ENABLED` to `true`
|
|
GOOGLE_LOGIN_ENABLED=false
|
|
|
|
BASE_URL='http://localhost:3000'
|
|
NEXT_PUBLIC_APP_URL='http://localhost:3000'
|
|
|
|
JWT_SECRET='secret'
|
|
# This is used so we can bypass emails in auth flows for E2E testing
|
|
PLAYWRIGHT_SECRET=
|
|
|
|
# To enable SAML login, set both these variables
|
|
# @see https://github.com/calendso/calendso/tree/main/ee#setting-up-saml-login
|
|
# SAML_DATABASE_URL="postgresql://postgres:@localhost:5450/cal-saml"
|
|
# SAML_ADMINS='pro@example.com'
|
|
|
|
# @see: https://github.com/calendso/calendso/issues/263
|
|
# Required for Vercel hosting - set NEXTAUTH_URL to equal your BASE_URL
|
|
# NEXTAUTH_URL='http://localhost:3000'
|
|
|
|
# Remove this var if you don't want Cal to collect anonymous usage
|
|
NEXT_PUBLIC_TELEMETRY_KEY=js.2pvs2bbpqq1zxna97wcml.oi2jzirnbj1ev4tc57c5r
|
|
|
|
# Used for the Office 365 / Outlook.com Calendar integration
|
|
MS_GRAPH_CLIENT_ID=
|
|
MS_GRAPH_CLIENT_SECRET=
|
|
|
|
# Used for the Zoom integration
|
|
ZOOM_CLIENT_ID=
|
|
ZOOM_CLIENT_SECRET=
|
|
|
|
#Used for the Daily integration
|
|
DAILY_API_KEY=
|
|
DAILY_SCALE_PLAN=''
|
|
|
|
# E-mail settings
|
|
|
|
# Cal uses nodemailer (@see https://nodemailer.com/about/) to provide email sending. As such we are trying to
|
|
# allow access to the nodemailer transports from the .env file. E-mail templates are accessible within lib/emails/
|
|
|
|
# Configures the global From: header whilst sending emails.
|
|
EMAIL_FROM='notifications@yourselfhostedcal.com'
|
|
|
|
# Configure SMTP settings (@see https://nodemailer.com/smtp/).
|
|
# Note: The below configuration for Office 365 has been verified to work.
|
|
EMAIL_SERVER_HOST='smtp.office365.com'
|
|
EMAIL_SERVER_PORT=587
|
|
EMAIL_SERVER_USER='<office365_emailAddress>'
|
|
# Keep in mind that if you have 2FA enabled, you will need to provision an App Password.
|
|
EMAIL_SERVER_PASSWORD='<office365_password>'
|
|
# ApiKey for cronjobs
|
|
CRON_API_KEY='0cc0e6c35519bba620c9360cfe3e68d0'
|
|
|
|
# Stripe Config
|
|
NEXT_PUBLIC_STRIPE_PUBLIC_KEY= # pk_test_...
|
|
STRIPE_PRIVATE_KEY= # sk_test_...
|
|
STRIPE_CLIENT_ID= # ca_...
|
|
STRIPE_WEBHOOK_SECRET= # whsec_...
|
|
PAYMENT_FEE_PERCENTAGE=0.005 # Take 0.5% commission
|
|
PAYMENT_FEE_FIXED=10 # Take 10 additional cents commission
|
|
|
|
# Application Key for symmetric encryption and decryption
|
|
# must be 32 bytes for AES256 encryption algorithm
|
|
CALENDSO_ENCRYPTION_KEY=
|
|
|
|
# Intercom Config
|
|
NEXT_PUBLIC_INTERCOM_APP_ID=
|