Single Page Application Demo using Engity IdP

This Single Page Application demonstrates the integration with the IdP (Identity Provider) of the Engity GmbH.

It is available at https://demo.engity.app.

TOC

1. Structure
2. Development
3. FAQ
4. License

Structure

• OpenID Connect: oidc-client-ts with react-oidc-context (src/lib/authentication.tsx)

  ℹ️ This project supports multiple sub-paths which are dynamically resolved (configured in src/environments/environment.ts). As a result, the authentication procedure is a little bit more complex as a regular application. Please keep this in mind.

• Basic Framework: React (entry point: src/index.tsx)

• Language: TypeScript (tsconfig.json)

• Build system: mise (mise.toml) and RSBuild (rsbuild.config.mts)

• Linting/Formatting: Biome (biome.jsonc)

• I18n: i18next with react-i18next (src/lib/i18n.ts)

• Router: React Router

• Theme: Radix UI with Lucide React

• Charts: React ApexCharts

Development

Requirements

1. Have at least mise 2026-05+ installed (mise --version)
2. Have a local CA for your mkcert installed (if not already done)

   mise run install:ca

3. Have all dependencies installed

   mise run install

Run

Run the local development server.

mise run serve

Now it will be available at:

1. https://local.engity.dev:4200
2. https://local.engity.dev:4200/passkey
3. https://local.engity.dev:4200/password
4. https://local.engity.dev:4200/social-logins
5. https://local.engity.dev:4200/magic-link
6. https://local.engity.dev:4200/username
7. https://local.engity.dev:4200/tfa-required
8. https://local.engity.dev:4200/tfa-forbidden
9. https://local.engity.dev:4200/existence-expose

ℹ️ If you cannot resolve the host, see FAQ: local.engity.dev cannot be resolved;

FAQ

local.engity.dev cannot be resolved

Some routers enabled a feature called DNS rebinding protection. These will prevent external domains (like local.engity.dev) to be resolved to 127.0.0.1. In this case you need either to tell your router to accept an exception for this domain or simply add an entry to your local /etc/hosts:

1. Open the hosts file on your operating system:
   • Linux/macOS

     sudo vi /etc/hosts

   • Windows

     sudo notepad c:\Windows\System32\drivers\etc\hosts

2. Ensure you have the following content:

   127.0.0.1  local.engity.dev
   ::1        local.engity.dev