Test your SAML/SCIM integration without setting up a full-blown Identity Provider
Go to file
Ulysse Carion 162dd87fc1
lib/saml: fix base64 encoding of SAML assertions for users with non-ASCII names (#16)
This PR fixes `encodeAssertion` to use btoa correctly for SAML
assertions that contain non-ASCII.

Messages are first manually encoded into UTF-8, and the resulting data
is coerced into a JS string that btoa will correctly encode. That
intermediary string isn't entirely meaningful -- JS strings are UTF-16,
not UTF-8 -- but I think this "hack" of sorts is tolerable given how
fleeting its use is.
2025-01-13 14:50:34 -08:00
public Move UI pages for app and login into pages router (#12) 2024-10-29 15:02:10 -07:00
src lib/saml: fix base64 encoding of SAML assertions for users with non-ASCII names (#16) 2025-01-13 14:50:34 -08:00
.env.development.local Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
.gitignore Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
.nvmrc scim: match /Users results in "Resources" or "resources" (#15) 2025-01-10 10:30:49 -08:00
.prettierignore spike: create assertions 2024-05-13 16:19:21 -07:00
.prettierrc.json spike: create assertions 2024-05-13 16:19:21 -07:00
components.json Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
LICENSE Nits + index page (#5) 2024-10-10 11:14:10 -07:00
next-env.d.ts Move UI pages for app and login into pages router (#12) 2024-10-29 15:02:10 -07:00
next.config.js Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
package-lock.json Move UI pages for app and login into pages router (#12) 2024-10-29 15:02:10 -07:00
package.json Move UI pages for app and login into pages router (#12) 2024-10-29 15:02:10 -07:00
postcss.config.js Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
README.md Add screenshot to README (#7) 2024-10-15 11:12:01 -07:00
screenshot.png Add screenshot to README (#7) 2024-10-15 11:12:01 -07:00
tailwind.config.js Move to Next.js (#2) 2024-10-03 09:57:43 -07:00
tsconfig.json Move to Next.js (#2) 2024-10-03 09:57:43 -07:00

DummyIDP

DummyIDP is a website you can use to test your application's SAML and SCIM support end-to-end. From your application's perspective, it's exactly like the identity provider ("IDP") your customers use, but unlike commercial IDPs there's no "input your email" or "talk to sales" step to use DummyIDP.

DummyIDP implements the "Identity Provider" side of the SAML and SCIM protocols. It is meant for use as a way to test your application's support for the "Service Provider" side of the SAML and SCIM protocols. See "DummyIDP Security Posture" for details.

Local development / self-hosting

DummyIDP is available for free online at https://dummyidp.com. You can also self-host it or hack on it locally.

DummyIDP is a Next.js application. It is deployed in production on Vercel. You can hack on it yourself by running:

npm install
npm run dev