Solution Architecture · Version 1.0
Norvia Backoffice Architecture
A standalone .NET control plane integrating the development Azure SQL database with either a product platform API or the supplied sandbox API.
1. Architecture drivers
- Loose coupling between central administration and individual Norvia products.
- Clear ownership: Norvia Backoffice owns catalogue and operator data; product platforms own their native accounts and roles.
- Support for a provider-defined product API and a standalone course sandbox.
- Local development uses the development environment’s Azure SQL database.
2. Logical architecture
BrowserRazor/MVC user interface
→
Norvia Backoffice.NET 10 web application
→
Azure SQLShared system of record
Application ServicesValidation, RBAC, audit, provisioning
→
Provisioning APIProduct-specific API or course sandbox
3. Component responsibilities
| Component | Responsibility |
|---|---|
| ASP.NET Core MVC | Server-rendered UI, model validation, authentication, role authorization, anti-forgery protection, and error handling. |
| Application layer | Use cases for products, roles, tenants, tenant admins, backoffice users, and provisioning orchestration. |
| Infrastructure layer | Azure SQL repositories, provisioning HTTP client, password hashing, structured logging, and audit persistence. |
| Azure SQL Database | Stores NorviaProducts, ProductUserRole, Tenant, UserExtended, and BackofficeUsers. |
| Provisioning API | Either the provider-documented product platform API or the standalone ProvisionTenantAdmin sandbox; returns a UserID. |
4. Data model
NorviaProducts1
── has ──ProductUserRolemany
Tenant1
── contains ──UserExtendedmany
BackofficeUsers is intentionally independent of tenant identities because internal Norvia operators do not belong to customer tenants. ProductUserRole.ProductRoleID is an external identifier owned by the selected product platform.
| Table | Purpose | Key controls |
|---|---|---|
| NorviaProducts | Technology-neutral product catalogue | Primary key; unique name enforced by application/migration |
| ProductUserRole | Maps Norvia role names to platform role IDs | FK to product; unique ProductID + ProductRoleID |
| Tenant | Customer organizations | Active flag; unique name |
| UserExtended | Tenant users and OutSystems identity mapping | FK to Tenant; nullable OutSystemsUserId until provisioned |
| BackofficeUsers | Internal application identities and roles | Unique email; constrained roles/status; hashed password in production |
5. Authorization design
| Capability | Super Admin | Admin | User |
|---|---|---|---|
| Products / Product Roles | Manage | Denied | Denied |
| Tenants | Manage | Manage | Denied |
| Tenant Admins / Provisioning | Manage | Manage | Denied |
| Backoffice Users | Manage | Denied | Denied |
6. Workflow designs
6.1 Product and product-role management
- Authorized Super Admin opens the relevant list.
- Application loads records from Azure SQL.
- User submits create/update data.
- Server validates required fields, uniqueness, integer IDs, and product relationship.
- Repository commits the transaction and the audit service records the change.
- Updated list and confirmation are returned.
6.2 Tenant onboarding
- Super Admin or Admin creates the customer tenant.
- Application validates uniqueness and inserts an active Tenant record.
- Operator creates a Tenant Admin linked through Tenant_ID.
- UserExtended is saved with no OutSystemsUserId; status is Not Provisioned.
- Operator may review/edit the local record before provisioning.
6.3 Tenant-admin provisioning
Validate local user→Resolve product role→Call selected API→Persist returned UserID→Audit outcome
- Reject the request if the user is inactive, already provisioned, or lacks required tenant/email/role data.
- Select the provider-documented product platform API or the standalone
ProvisionTenantAdminsandbox. - Call the selected API over TLS using server-held credentials.
- On a successful response, validate the returned UserID and update
UserExtended.OutSystemsUserIdtransactionally. - On product API timeout or failure, keep OutSystemsUserId null, store diagnostic status, and allow a safe retry.
6.4 Backoffice login and authorization
- User submits email and password over HTTPS.
- Application finds the normalized unique email and verifies the salted password hash.
- Inactive users are rejected.
- A secure, HttpOnly, SameSite cookie is issued with the role claim.
- Authorization policy checks every protected action; denied attempts are audited.
7. Security and operations
- Azure SQL permits only required application connectivity; local application credentials use least privilege against the development database.
- Real product API secrets remain outside source control and logs.
- Passwords use ASP.NET Core Identity-compatible adaptive hashing.
- Outbound product API calls use timeouts, bounded retries with backoff, correlation IDs, and redacted structured logs.
- Errors, failed logins, and provisioning failures are recorded for troubleshooting.