A simple mock SAML 2.0 Identity Provider
Go to file
dependabot[bot] fb5113d73d
build(deps-dev): bump @typescript-eslint/parser from 8.58.0 to 8.58.1 (#1167)
Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 8.58.0 to 8.58.1.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.58.1/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/parser"
  dependency-version: 8.58.1
  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>
2026-04-08 17:12:18 +01:00
.github build(deps): bump docker/login-action from 3 to 4 (#1139) 2026-03-09 22:01:41 +00:00
components chore: tailwind 4 update (#1085) 2025-12-15 11:29:26 +00:00
lib chore: support VERCEL_BRANCH_URL for preview deployments (#1073) 2025-12-05 17:18:08 +00:00
pages chore: tailwind 4 update (#1085) 2025-12-15 11:29:26 +00:00
public updated logo 2022-05-22 19:57:08 +01:00
styles chore: tailwind 4 update (#1085) 2025-12-15 11:29:26 +00:00
types Cleanup 2022-02-18 09:37:27 +05:30
utils updated saml20 (#534) 2024-03-08 13:34:09 +00:00
.dockerignore Optimise multi platform build (#128) 2022-12-09 15:04:40 +00:00
.env.example fixed build when NEXT_PUBLIC_GTM_ID is not defined 2022-03-01 13:31:28 +00:00
.gitignore added vscode to gitignore 2024-02-04 15:39:25 +00:00
.prettierignore build(deps): bump the next group with 2 updates (#758) 2024-10-22 20:21:56 +03:00
.prettierrc.js prettier fix 2024-02-04 15:38:33 +00:00
.release-it.json added release-it 2023-12-25 12:15:10 +00:00
app.json prettier fix 2024-02-04 15:38:33 +00:00
Dockerfile updated node (#963) 2025-05-29 12:32:14 +01:00
eslint.config.cjs build(deps): bump the next group with 2 updates (#1045) 2025-11-17 00:25:50 +00:00
LICENSE added license file 2022-02-23 17:16:41 +00:00
next-env.d.ts build(deps): bump the next group with 2 updates (#1045) 2025-11-17 00:25:50 +00:00
next.config.js npm update and cleanup of experimental options 2024-12-19 13:36:00 +00:00
package-lock.json build(deps-dev): bump @typescript-eslint/parser from 8.58.0 to 8.58.1 (#1167) 2026-04-08 17:12:18 +01:00
package.json build(deps-dev): bump @typescript-eslint/parser from 8.58.0 to 8.58.1 (#1167) 2026-04-08 17:12:18 +01:00
postcss.config.js chore: tailwind 4 update (#1085) 2025-12-15 11:29:26 +00:00
Procfile Oneclick deploy button (#2) 2022-02-28 21:54:20 +00:00
README.md Update README.md 2024-04-03 19:11:16 +01:00
tailwind.config.js chore: tailwind 4 update (#1085) 2025-12-15 11:29:26 +00:00
tsconfig.json build(deps): bump the next group with 2 updates (#1045) 2025-11-17 00:25:50 +00:00

Mock SAML from BoxyHQ

Deploy Deploy with Vercel

Mock SAML is a free SAML 2.0 Identity Provider for testing SAML SSO integrations.

Namespaces

Try Mock SAML, our free hosted service. Whilst we use the root domain for our own testing you can create your own unique namespace by navigating to https://mocksaml.com/namespace/any_name_of_your_choice.

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

Refer to env.example for instructions on how to create the key pair. 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)