Leobit
An Authentication Solution for the Multi-Tenant Asset Management Platform
Software modernization for the UK-based provider of proptech software
ABOUT the project
- Client:
- Proptech and Asset Management Company
- Location:
-
UK
- Company Size:
- 10+ Employees
- Industry:
- Real Estate
- Solution:
- Custom Software
Technologies:
Leobit helped a UK-based proptech company modernize the user authentication solution for their multi-tenant platform for managing real estate assets. The platform is used by tenants, public service providers, and property owners. By retiring legacy parts of the solution and preserving all the critical features, data sources, and connections in a modern schema stored in a unified database we made the solution more manageable. The modernization also enhanced software security and performance, adjusting it to modern industry standards.
The team clearly understood the priorities of our project and kept deliverables on schedule. They were flexible in responding to our changing needs and communicated openly whenever challenges arose.
Customer
Our customer is a UK-based real estate company that provides a multi-tenant asset management platform. The solution provides functionality for monitoring and managing properties to tenants, public service providers, and property owners. The system includes a comprehensive authentication solution, which the client decided to modernize in order to meet modern industry standards.
Business Challenge
The customer planned to retire their existing IdentityServer setup and replace it with OpenIddict framework for authentication and authorization. This would allow them to enhance identity management, reduce operational risks, and align the authentication solution with modern industry standards.
The key challenge lay in the fact that identity-related data and configurations were fragmented across multiple locations, and organizing them in a single location would require strong technical experience. In addition, the project had to be completed within tight deadlines.
Why Leobit
The customer was impressed by our strong experience, proven by a significant track record of successful projects. They were also satisfied with our expertise in technologies that were critical to their solution. Finally, our vision and business values aligned.
Project
in detail
We had to modernize the customer’s data architecture within a limited time. Upon analyzing their requirements and their current system, we jumped into work on modernization.
Our specialists unified data from different databases in a new schema located in the main SQL Server database. Our specialists centralized user identity data to create a single source of truth, ensuring greater system consistency. We also aligned the authorization configuration authentication and recreated all the critical parts and connections of the original database and schema in the new infrastructure setup.
Our team decommissioned all the legacy or unnecessary parts of the infrastructure to enhance its productivity and reduce the customer’s technical debt. We also enhanced the system with some new features, such as the QR code for system enrollment, to improve user experience.
Our full-stack developers used Blazor Server to build a simple yet convenient user authentication interface. Upon completing the major work on the project, our QA specialists tested the system to ensure a consistent and bug-free user experience.
Consolidated Identity and Access Management
Our specialists successfully unified identity data from two different locations:
- The SecurityDB that contained the old ASP.NET Membership schema and the ASP.NET Identity tables.
- The SECURITY schema in the SQL Server database, which held the IdentityServer configuration.
Such a split increased the customer’s maintenance overhead, causing issues with troubleshooting and making changes to authentication flows slower and riskier.
We recreated all the parts and connections of the original schema and database in the new IDENTITY schema stored in the SQL database. In fact, we preserved the system’s local and Microsoft Entra ID authentication flows and recreated the core system configurations.
Decommissioned of Legacy System Components
Upon successfully consolidating the components from the SecurityDB and the SECURITY schema, we decommissioned obsolete parts of the original setup. In particular, we decommissioned the SecurityDB and the unrequired parts of the original SECURITY schema located in the SQL Server database. This made the platform more manageable and performant, as some unnecessary workflows and data that consumed both CPU and storage were eliminated.
New Features Added Upon System Modernization
To enhance system performance, ensure better data organization and traceability, ultimately modernizing the authentication workflow, we introduced some new components in the new database. For example, we introduced a new IDENTITY schema and extended the new authenticator to support multi-factor authentication using Google Authenticator or Microsoft Authenticator for local accounts. Our specialists also added the QR code generation feature for system enrollment.
Technology Solutions
- Centralization of the customer’s assets from the SecurityDB and the SECURITY schema in the new IDENTITY schema stored in the main SQL Server database.
- Updated system configurations in the OpenIddict framework to fit multiple application types (web, mobile, and APIs).
- Support for both multi-tenant and single-tenant scenarios.
- Added multi-factor authentication through Google Authenticator or Microsoft Authenticator for local accounts.
Value Delivered
- Lower operational costs because the system is less challenging maintain, back up, secure, and monitor.
- Reduced risk due to the removal of legacy components and minimization of integration points that can fail or drift out of sync.
- Faster delivery of new features, as identity changes no longer require coordinating updates across multiple systems.
- Adherence to modern industry standards.
- Clear and well-organized documentation on all migration steps, as well as efficient and reliable rollback mechanics.
- Clear ownership and governance of identity data.
