useraccount-api
.NET 8 FastEndpoints API for Phenix user accounts — loading/searching users from MongoDB, mapping SSO email aliases to sales persons, resolving user branch relationships and gold status, and serving 'view as' configuration for head-office users.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | ASP.NET Core 8, FastEndpoints 8, Serilog |
| Runtimes | .NET 8 |
| Tests / CI | good / CI in place |
| Last commit | 2026-07-01 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Identity and access (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | AWS Deployed to AWS
|
| Releases | 0 release pipeline(s): |
| Integration | rest, jwt |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Pinning dependency: phenix-feature-service
Detaches when its pinning dependencies are cut or multi-targeted (phenix-feature-service).
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
No excuseNothing technical is holding this repo on the three-week release. It either already deploys without downtime (AWS) or is a modern, well-tested service the automated stealth path can carry today. Already deploys as a container to AWS, which releases without downtime today. Separating it from the three-week release is a process decision, not a technical one.
- Feature flags come from phenix-feature-service (WCF-only): flag reads themselves are a legacy dependency to watch
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Use ECS rolling deployments with health checks gating traffic, and take this service off the three-week release train.
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Already containerisedIts pipelines already build containers and deploy to AWS. Nothing to do here.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
useraccount-api
Purpose
The modern user-account service for Phenix identities. Vertical-slice endpoints cover users (get, get-all, batch, search, users-by-SSO-email, user branches), SSO aliases (add/delete/list per sales person — bridging the IdP's SSO email to the internal SalesPersonId when the two differ), gold-status calculation, and "view as" endpoints letting head-office users resolve which account to impersonate per application. Two substantial docs explain SSO alias semantics and branch resolution.
Tech stack
C# on .NET 8 (three source projects: Api, Common, DataAccess). FastEndpoints 8 with FastEndpoints.Swagger, Phenix.Auth.JWTBearer authentication, Serilog with compact JSON formatting, config-driven CORS, MongoDB.Driver 3.8 via TC.ConnectionBroker.Mongo with TC.ScriptRunner.Mongo initialisation, WebApi.Logger, TC.Diagnostics health checks plus a custom data-store health check.
Deployment
Included as prod_application with 0 releases — YAML/AWS only. Build pipeline useraccount-api from azure-pipelines.yml on the shared InternalOSS/azure-pipelines-templates jobs/ci.yml (SDK 8.x): container built into the phenix namespace and deployed to ECS with tfvars, eu-west-1, functional area phenix (unlike the cx-public siblings). Per-environment appsettings (qa, preproduction, production).
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker), TC.Exceptions.WebApiClient.AspNetCore (tc-exceptions), TC.Diagnostics.HealthChecks (tc-diagnostics-portal), TC.Phenix.CompanyInfo (company-info-api) and TC.Phenix.Feature (phenix-feature-service) for active-company filtering and feature gates. Phenix.Auth.JWTBearer and WebApi.Logger map to no included repo. No external third-party services.
Data stores
Reads/writes three MongoDB databases through the connection broker: UserAccounts (user accounts, SSO aliases — shared with backoffice-useraccount-service and read by tc-performance), Gold (gold-status groups, owned by tc-gold-api) and ViewingAs (view-as configuration, shared with viewing-as-api). It owns none of them exclusively, so schema changes ripple across at least four repos.
Integration points
Inbound REST with Phenix JWT bearer auth and config-driven CORS; no outbound service calls (company info and features come via packages/broker), no bus or streams.
Code health
Good: two test projects with ~140 facts/theories over services, mappers and Mongo repositories, and a genuinely useful README plus docs/ on SSO alias and branch-resolution behaviour — among the better-documented repos in the estate. Actively developed (last commit 2026-07-01).
Modernisation risks
Low as a codebase — current .NET 8, tested, documented, containerised. The structural risk is data coupling: three Mongo databases shared with backoffice-useraccount-service, tc-gold-api, tc-performance and viewing-as-api mean no single owner of the user-account schema, and the estate still runs multiple overlapping user-account services (this, backoffice-useraccount-service, backoffice-useraccount-legacy, mytc-user-service) whose consolidation path is undocumented.