A simple mock SAML 2.0 Identity Provider
Go to file
2022-01-13 23:20:16 +05:30
components wip 2022-01-13 22:37:44 +05:30
pages wip 2022-01-13 23:20:16 +05:30
prisma first commit 2022-01-09 12:58:39 +05:30
public Initial commit from Create Next App 2022-01-08 20:41:13 +05:30
services wip 2022-01-13 23:20:16 +05:30
styles wip 2022-01-13 22:37:44 +05:30
types wip 2022-01-13 23:20:16 +05:30
.eslintrc.json Initial commit from Create Next App 2022-01-08 20:41:13 +05:30
.gitignore first commit 2022-01-09 12:58:39 +05:30
next-env.d.ts Initial commit from Create Next App 2022-01-08 20:41:13 +05:30
next.config.js Initial commit from Create Next App 2022-01-08 20:41:13 +05:30
package-lock.json wip 2022-01-13 22:37:44 +05:30
package.json wip 2022-01-13 22:37:44 +05:30
postcss.config.js wip 2022-01-13 22:37:44 +05:30
README.md wip 2022-01-13 22:37:44 +05:30
tailwind.config.js wip 2022-01-13 22:37:44 +05:30
tsconfig.json Initial commit from Create Next App 2022-01-08 20:41:13 +05:30

Backlog

  • Form validation
  • UI
  • Add timestamp to tables
  • Feed 10 users
  1. Autogenerate certificate
  2. Request validation
  3. Add logs to all request

SAML certificate (PEM format)

you need to generate a set of public and private keys and an X.509 certificate that contains the public key. The public keys and certificates must be generated with either the RSA or DSA algorithm and registered with Google.

/apps/

ACS URL Entity ID

Certificate -> Use same Certificate for all apps

Metadata Properties

  • entityID (IdP identity)
  • validUntil (Hard coded)
  • X509Certificate (Hard coded)
  • SingleSignOnService -> Binding

/apps/metadata -> Download