Integrate LoginMaster into your project
LoginMaster offers official TypeScript and .NET libraries that simplify integration by automatically handling encrypted communication, authentication, and dual-signature token verification. Prefer doing it your own way? You can integrate directly via REST APIs with any language, or develop your own custom library.
Official libraries
The official libraries handle encrypted communication with the tenant, authentication, and dual-signature token verification. If you prefer, you can integrate directly via REST APIs with any language or develop your own library.
TypeScript
Official library for Node.js, browser, and frameworks such as Next.js, Nuxt, Express, and similar. Handles authentication, dual-signature token verification, and encrypted communication with the tenant.
- Compatible with Node.js, browsers, and all major frameworks
- Automatic encrypted communication management with the tenant
- Built-in dual-signature token verification
- Full typing for an optimal developer experience
.NET
Official library for .NET applications (C#). Natively integrates with ASP.NET Core, Blazor, and any .NET project. Handles the entire authentication flow and secure communication with the tenant.
- Compatible with ASP.NET Core, Blazor, and any .NET project
- Ready-to-use middleware for authentication and authorization
- Automatic encrypted communication management with the tenant
- Built-in dual-signature token verification
Prefer a direct integration?
The official libraries are not mandatory. LoginMaster exposes standard REST APIs that you can use directly from any language or framework. You can also develop your own custom library to tailor the integration to your project's specific requirements.
Integration architecture
LoginMaster uses a multi-layer architecture with dedicated cryptographic keys for each component. Each project has its own key, each tenant communicates with the cloud independently, and tokens are signed by both.
REST API
LoginMaster exposes REST APIs for integration with customer projects. The official libraries simplify API access, but it is possible to integrate directly without a library, using any language or framework that supports HTTP calls.
- RESTful endpoints for authentication and user management
- Dedicated cryptographic key for each project
- Integrable with any language or framework
- User and device subjects, API keys, AWS IoT support with MQTT
Multi-Layer Secure Communication
Every communication in LoginMaster is protected by dedicated cryptographic keys at each level. The project communicates with the tenant via a specific key, the tenant communicates with the cloud via another key, and the client uses a separate cryptographic certificate.
- Project ↔ Tenant: per-project cryptographic key
- Tenant ↔ Cloud: per-tenant cryptographic key
- Client ↔ API: separate cryptographic certificate
- Encrypted payloads on all communications
SSO with Google and Microsoft
LoginMaster will support Single Sign-On with Google Workspace and Microsoft Entra ID by the end of Q2. Users will be able to authenticate via their corporate Google or Microsoft account, simplifying access and reducing credential management.
- Google Workspace SSO — available by end of Q2
- Microsoft Entra ID SSO — available by end of Q2
- Access with existing corporate account
- Configuration from the admin panel
Subjects and communication methods
LoginMaster distinguishes between subjects (who communicates) and communication methods (how they communicate). User and device are subject types, API keys are a server-to-server communication method. Native AWS IoT support with MQTT for devices.
User (Subject)
User-type subject: authentication via email and password, with optional 2FA support. Represents people who access applications.
Device (Subject)
Device-type subject: dedicated authentication for IoT devices and embedded systems. Native AWS IoT support with MQTT protocol for secure real-time communications.
API Key (Method)
Server-to-server communication method. API keys allow backend services and applications to communicate with LoginMaster without human intervention, ideal for microservices and automations.
Multi-layer secure communication
Each layer of the LoginMaster architecture uses dedicated and independent cryptographic keys. Key separation ensures that the compromise of one layer does not impact the others.
Project ↔ Tenant
Each project has a unique cryptographic key to communicate with its own tenant. This key is generated at project creation and encrypts all exchanged payloads.
Tenant ↔ Cloud
The tenant communicates with the LoginMaster Cloud via a cryptographic key specific to that tenant. This layer handles token validation and dual signing.
Client ↔ API
The communication between the client (browser, app, device) and the APIs uses a separate cryptographic certificate, independent from the project and tenant keys.
Per-project configuration
2FAConfigurable as disabled, optional, or mandatory for each project
Roles and PermissionsCustomizable roles with granular permissions for each project
Redirect URLsCustomizable URLs for post-setup, post-password reset, and post-2FA configuration
SSO ProviderGoogle Workspace and Microsoft Entra ID available by end of Q2
Subjects and APIsUser and device subjects, API keys for server-to-server communication, AWS IoT support with MQTT
Compatibility and integrations
LoginMaster integrates with any web, mobile, or IoT device application via the official libraries or REST APIs. SSO with Google Workspace and Microsoft Entra ID available by end of Q2.
Google Workspace (SSO)
Single Sign-On with Google Workspace, available by end of Q2. Users on your Google domain will be able to access your LoginMaster project directly with their corporate credentials, without creating a separate account.
Microsoft Entra ID (SSO)
Single Sign-On with Microsoft Entra ID (formerly Azure AD), available by end of Q2. Users will be able to authenticate with their corporate Microsoft account, seamlessly integrating into Microsoft environments.
Web and Mobile Applications
Any web or mobile application can integrate with LoginMaster via the official libraries (TypeScript, .NET) or directly via REST APIs. The project communicates with the tenant using the dedicated cryptographic key.
IoT Devices and AWS IoT
Devices are a subject type in LoginMaster. Native AWS IoT support with MQTT protocol for secure real-time communications. Each device is registered as an autonomous subject in the project.
Frequently Asked Questions About Integration
The easiest way is to use the official TypeScript or .NET libraries, which automatically handle encrypted communication with the tenant, authentication, and dual-signature token verification. If you prefer, you can integrate directly via LoginMaster's REST APIs with any language or framework, or develop your own custom library.
Yes. The official libraries simplify integration, but LoginMaster exposes standard REST APIs that you can use directly from any language or framework. You can also develop your own custom library. Each project communicates with its own tenant via a dedicated cryptographic key, and communication occurs on encrypted channels at every level.
LoginMaster will support Single Sign-On with Google Workspace and Microsoft Entra ID by the end of Q2. Configuration will be done from the tenant's admin panel and will allow users to access with their corporate Google or Microsoft account.
Yes, devices are a subject type in LoginMaster, distinct from users. LoginMaster offers native AWS IoT support with MQTT protocol for secure real-time communications. Each device is registered as an autonomous subject in the project with specific credentials and configurable permissions.
API keys are a communication method in LoginMaster, not a subject type. They allow backend services and automations to communicate with LoginMaster without human intervention. Each API key has configurable roles and permissions and is tied to the specific project within the tenant.
Official libraries are available for TypeScript (compatible with Node.js, browsers, and all major frameworks) and .NET (compatible with ASP.NET Core, Blazor, and any .NET project). For other languages, you can integrate directly via REST APIs or develop your own library.
Ready to integrate LoginMaster?
Choose the official TypeScript or .NET library, or integrate directly via REST APIs. Our technical team supports you at every stage of the integration.