Mock SAML is a free SAML 2.0 Identity Provider for testing SAML SSO integrations.
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.
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-samlRefer 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.
Set ALLOWED_EMAIL_DOMAINS to a comma-separated list to control which email domains can sign in. An entry is an exact domain (example.com), a subdomain wildcard (*.ory.dev matches abc.ory.dev but not ory.dev), or * for any domain. The default is example.com,example.org. When the list contains a wildcard, the login form shows a free-text domain field. The login page also accepts ?email=user@domain to prefill the form.
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
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.
- Discord (For live discussion with the Open-Source Community and BoxyHQ team)
- Twitter (Follow us)
- GitHub Issues (Contributions, report issues and product ideas)