5bbfaa98e4
* added cosign action * installing cosign using brew * minor fix * added actions step * removed the condition for testing * moved the cosign part to bottom * fixed cosign path * trying out moving some pieces * commented if condition * removed conditions for testing * uncommented if conditions Co-authored-by: Deepak Prabhakara <deepak@boxyhq.com> |
||
|---|---|---|
| .github | ||
| .husky | ||
| .vscode | ||
| _dev | ||
| components | ||
| e2e | ||
| hooks | ||
| lib | ||
| npm | ||
| pages | ||
| public | ||
| styles | ||
| swagger | ||
| .dockerignore | ||
| .env.example | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.js | ||
| Dockerfile | ||
| LICENSE | ||
| Procfile | ||
| README.md | ||
| SECURITY.md | ||
| app.json | ||
| next-env.d.ts | ||
| next.config.js | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| postcss.config.js | ||
| prettier.config.js | ||
| tailwind.config.js | ||
| tsconfig.json | ||
README.md
SAML Jackson (not fiction anymore)
SAML service [SAML in a box from BoxyHQ]
You need someone like Jules Winnfield to save you from the vagaries of SAML login. Jackson implements the SAML login flow as an OAuth 2.0 flow, abstracting away all the complexities of the SAML protocol.
Documentation
For full documentation, visit boxyhq.com/docs/jackson/introduction
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.
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 else 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: