A simple mock SAML 2.0 Identity Provider
2942a29d4e
Bumps [prettier-plugin-tailwindcss](https://github.com/tailwindlabs/prettier-plugin-tailwindcss) from 0.5.5 to 0.5.6. - [Release notes](https://github.com/tailwindlabs/prettier-plugin-tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/prettier-plugin-tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/prettier-plugin-tailwindcss/compare/v0.5.5...v0.5.6) --- updated-dependencies: - dependency-name: prettier-plugin-tailwindcss dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| components | ||
| lib | ||
| pages | ||
| public | ||
| styles | ||
| types | ||
| utils | ||
| .dockerignore | ||
| .env.example | ||
| .eslintrc.json | ||
| .gitignore | ||
| .prettierrc.js | ||
| app.json | ||
| Dockerfile | ||
| LICENSE | ||
| next-env.d.ts | ||
| next.config.js | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| Procfile | ||
| README.md | ||
| tailwind.config.js | ||
| tsconfig.json | ||
Mock SAML from BoxyHQ
Mock SAML is a free SAML 2.0 Identity Provider for testing SAML SSO integrations.
Try Mock SAML, our free hosted service.
Source code visualizer
Install
With Docker
The docker container can be found at boxyhq/mock-saml.
docker run \
-p 4000:4000 \
-e APP_URL="http://localhost:4000" \
-e ENTITY_ID="https://saml.example.com/entityid" \
-e PUBLIC_KEY="<PUBLIC_KEY>" \
-e PRIVATE_KEY="<PRIVATE_KEY>" \
-d boxyhq/mock-saml
Replace <PUBLIC_KEY> with Base64 encoded value of public key.
Replace <PRIVATE_KEY> with Base64 encoded value of private key.
Without Docker
git clone https://github.com/boxyhq/mock-saml.git
cd mock-saml
Install dependencies
npm install
Update .env with your own keys.
cp .env.example .env
Build the Next.js app.
npm run build
Run the Mock SAML server.
npm run start
Contributing
Thanks for taking the time to contribute! Contributions make the open-source community a fantastic place to learn, inspire, and create. Any contributions you make are greatly 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.
Community
- Discord (For live discussion with the Open-Source Community and BoxyHQ team)
- Twitter (Follow us)
- GitHub Issues (Contributions, report issues and product ideas)