The ts/ folder contains the server runtime for idp.global: startup, website server wiring, typed routes, OIDC endpoints, passport approval APIs, alerting, and the core Reception managers.

Issue Reporting and Security

For reporting bugs, issues, or security vulnerabilities, please visit community.foss.global/. This is the central community hub for all issue reporting. Developers who sign and comply with our contribution agreement and go through identification can also get a code.foss.global/ account to submit Pull Requests directly.

What Lives Here

index.ts boots the service, loads env vars, starts the website server, and mounts OIDC endpoints.
reception/classes.reception.ts creates the service container and initializes all managers.
reception/ contains the domain logic for users, sessions, orgs, roles, invites, apps, billing, passport devices, alerts, abuse protection, and OIDC.
plugins.ts centralizes external imports used by the backend.

Startup Behavior

The backend startup in ts/index.ts does four main things:

Loads runtime configuration from .nogit and the working directory.
Creates a UtilityWebsiteServer that serves the built frontend.
Registers OIDC endpoints such as discovery, JWKS, authorize, token, userinfo, and revoke.
Creates and starts Reception, then starts HTTP serving on port 2999.

Required Environment

export MONGODB_URL=mongodb://localhost:27017/idp-dev
export IDP_BASEURL=http://localhost:2999
export INSTANCE_NAME=idp-dev

Optional:

SERVEZONE_PLATFORM_AUTHORIZATION
PADDLE_TOKEN
PADDLE_PRICE_ID

Key Managers

Class	Responsibility
`JwtManager`	JWT issuance, validation, and key rotation support
`LoginSessionManager`	Session creation, refresh, logout, and session metadata
`RegistrationSessionManager`	Registration flow state
`UserManager`	User-centric queries and mutations
`OrganizationManager`	Organization creation and access checks
`RoleManager`	Role and permission management
`UserInvitationManager`	Invitations, member updates, and ownership transfer
`BillingPlanManager`	Billing plan state and Paddle config endpoint
`AppManager`	Global app administration
`AppConnectionManager`	App connection tracking
`ActivityLogManager`	User activity logging
`AlertManager`	Passport alerts and alert rule management
`AbuseProtectionManager`	Attempt windows and temporary blocks for sensitive flows
`PassportManager`	Trusted device enrollment, approval challenges, dashboard data, and signed device requests
`PassportPushManager`	Push notification delivery hooks for passport challenges and alerts
`OidcManager`	OIDC discovery, auth code flow, token exchange, userinfo, revoke

Passport Request Surface

The backend exposes signed-device workflows over the same typedrequest router as the rest of the service:

enrollment: createPassportEnrollmentChallenge, completePassportEnrollment
devices: getPassportDevices, revokePassportDevice, registerPassportPushToken
challenges: createPassportChallenge, approvePassportChallenge, rejectPassportChallenge, listPendingPassportChallenges
dashboard and hints: getPassportDashboard, getPassportChallengeByHint, markPassportChallengeSeen
alerts: listPassportAlerts, getPassportAlertByHint, markPassportAlertSeen, dismissPassportAlert

Local Development

From the repository root:

pnpm install
pnpm build
pnpm watch

The watch setup runs the backend from ts/ and rebuilds the frontend bundle from ts_web/.

License and Legal Information

This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the license file.

Please note: The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.

Trademarks

This project is owned and maintained by Task Venture Capital GmbH. The names and logos associated with Task Venture Capital GmbH and any related products or services are trademarks of Task Venture Capital GmbH or third parties, and are not included within the scope of the MIT license granted herein.

Use of these trademarks must comply with Task Venture Capital GmbH's Trademark Guidelines or the guidelines of the respective third-party owners, and any usage must be approved in writing. Third-party trademarks used herein are the property of their respective owners and used only in a descriptive manner, e.g. for an implementation of an API or similar.

readme.md

ts/ Backend Module