0b99c7d667
* updated typeorm * renamed connection * updated migration scripts to new TypeORM version (v3) * typeorm and mongo -migrations and namespace column * update the mongo migration file * remove the camelcase * remove camelcase * rename the file * renaming migration files * folder restructuring and add migrate-mongo package * correcting path and minor changes * merging db name with URL * changing ts to js for mongo * migration automation with env variable * using custom scripts for migration * Dockerfile fixes * bootstrap script fixes and still need ts-node migrate-mongo in dockerfile * running migration in CI/CD * turning down planetscale * migration related fixes for namespace * Migration & bootstrap changes * reverting minor change * bootstrap.sh will only run in docker env * bootstrap RUN_MIGRATION env variable will use true * migration fixes * migration changes * removed console logs * planetscale migration fixes * copied back old files, tweaks to filenames * add index for namespace * restore older migration scripts * formatting * aligned timestamps * updated mysql, mariadb, mssql, planetscale namespace migrations * We'll run migrate manually as a separate step/container * forgot to add migrate.sh * bumped up timestamp * Enable planetscale testing * Revert planetscale test and comment config object * Revert deletions in Dockerfile * Update maria, mssql, mysql, ps, pg, sql namespace migrations * Cleanup * Add runMigration env to support manual run * Minor tweak * Ensure sql data migrations run after schema changes * Fix mssql namespace data migration query * Sync lock file * Update mongo timestamp * Set env for npm mongo migration script * [sql] Populate namespace column for synchronize: true instances * Rename `DB_RUN_MIGRATION` -> `DB_MANUAL_MIGRATION` * [mongo] Populate namespace for already deployed instances * Cleanup migrate.sh * [bash -> sh] bash does not work inside docker * Optimise migration artifacts * Source packages from global path * Copy npm from build context - excludes node_modules via .dockerignore * Remove redundant copy step * added swc packages * fresh package-lock * fresh package-lock * added migratepg job to skaffold fixes in migrate.sh to exit with error when migration fails * cleanup * added migratepg to demo skaffold as well * turn on planetscale tests --------- Co-authored-by: Deepak Prabhakara <deepak@boxyhq.com> Co-authored-by: Utkarsh Mehta <ukrocks.mehta@gmail.com> Co-authored-by: Aswin V <vaswin91@gmail.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| _dev | ||
| components | ||
| e2e | ||
| ee | ||
| kustomize | ||
| lib | ||
| locales/en | ||
| npm | ||
| pages | ||
| public | ||
| styles | ||
| swagger | ||
| types | ||
| .dockerignore | ||
| .env.example | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.js | ||
| .release-it.json | ||
| CODE_OF_CONDUCT.md | ||
| Dockerfile | ||
| LICENSE | ||
| Procfile | ||
| README.md | ||
| SECURITY.md | ||
| app.json | ||
| i18next.d.ts | ||
| middleware.ts | ||
| migrate.sh | ||
| next-env.d.ts | ||
| next-i18next.config.js | ||
| next.config.js | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| postbuild.ts | ||
| postcss.config.js | ||
| prebuild.ts | ||
| skaffold-demo-services.yaml | ||
| skaffold-demo.yaml | ||
| skaffold-dynamodb.yaml | ||
| skaffold-mariadb.yaml | ||
| skaffold-mongo.yaml | ||
| skaffold-mssql.yaml | ||
| skaffold-mysql.yaml | ||
| skaffold-postgres.yaml | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| types.ts | ||
README.md
Participating in
⬆️ Take a look at our Issues ⬆️
· Explore the docs »
· SaaS Early Access »
⭐️ SAML Jackson: Enterprise SSO made simple
🚀 Getting Started with SAML Jackson
Please star ⭐ the repo if you want us to continue developing and improving SAML Jackson! 😀
Streamline your web application's authentication with Jackson, an SSO service supporting SAML and OpenID Connect protocols. Beyond enterprise-grade Single Sign-On, it also supports Directory Sync via the SCIM 2.0 protocol for automatic user and group provisioning/de-provisioning.
There are two ways to integrate SAML Jackson into an application. Depending on your use case, you can choose either of them.
- separate service (Next.js application) Admin Portal out of the box for managing SSO and Directory Sync connections.
- NPM library as an embedded library in your application.
SAML/OIDC SSO service
Jackson implements the SAML login flow as an OAuth 2.0 or OpenID Connect flow, abstracting away all the complexities of the SAML protocol. Integrate SAML with just a few lines of code. We also now support OpenID Connect providers.
Try our hosted demo showcasing the SAML SP login flow here, no SAML configuration required thanks to our Mock SAML service.
🎦 Videos
- SSO/OIDC Tutorial SAML Jackson Enterprise SSO (split into chapters to easily find what you are looking for)
- SAML single sign-on login demo
✨ Demo
Here is what deploying SSO looks like with and without BoxyHQ
Documentation
For full documentation, visit boxyhq.com/docs/jackson/overview
Directory Sync
SAML Jackson also supports Directory Sync based on the SCIM 2.0 protocol.
Directory sync helps organizations automate the provisioning and de-provisioning of their users. As a result, it streamlines the user lifecycle management process by saving valuable organizational hours, creating a single truth source of the user identity data, and facilitating them to keep the data secure.
For complete documentation, visit boxyhq.com/docs/directory-sync/overview
Source code visualizer
Observability
We support first-class observability on the back of OpenTelemetry, refer here for more details.
SBOM Reports (Software Bill Of Materials)
We support SBOM reports, refer here for more details.
Container Signing and Verification
We support container image verification using cosign, refer here for more details.
Development Setup
Database
To get up and running, we have a docker-compose setup that will spawn all the supported databases. Ensure that the docker daemon is running on your machine and then run: npm run dev-dbs. In case you need a fresh start, destroy the docker containers using: npm run dev-dbs-destroy and run: npm run dev-dbs.
Development server
Copy the .env.example to .env.local and populate the values. Have a look at https://boxyhq.com/docs/jackson/deploy/env-variables for the available environment variables.
Run the dev server:
# Install the packages
npm run custom-install
# Start the server
npm run dev
End-to-End (E2E) tests
Create a .env.test.local file and populate the values. To execute the tests run:
npm run test:e2e
🖳 Contributing
Thanks for taking the time to contribute! Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make will benefit everybody and are appreciated.
Please try to create bug reports that are:
- Reproducible. Include steps to reproduce the problem.
- Specific. Include as much detail as possible: which version, what environment, etc.
- Unique. Do not duplicate existing opened issues.
- Scoped to a Single Bug. One bug per report.
💫 Support
Reach out to the maintainers at one of the following places:
- GitHub Discussions
- GitHub Issues (Bug reports, Contributions)
🤩 Community
- Discord (For live discussion with the Open-Source Community and BoxyHQ team)
- Twitter (Follow us)
- Youtube (Watch community events and tutorials)