Skip to main content

User Lifecycle

Summary​

User lifecycle ownership is transitional: the extracted identity service stores lifecycle state and implements selected self-service security operations, while creation and administration operations remain in the active monolith.

Audience​

  • Platform and customer administrators
  • Support and implementation teams
  • Developers and QA engineers
  • Product owners and solution architects

Purpose​

This page separates confirmed operations from data-model foundations so that an entity or status field is not mistaken for a completed user-management workflow.

Architecture​

The diagram combines confirmed states with explicitly labeled transitional or unconfirmed lifecycle operations.

Business concepts​

Lifecycle areaStatusConfirmed evidence
InvitationRequires confirmationNo invitation endpoint or invitation entity is exposed by identity service.
RegistrationTransitionalRegistration/user creation exists in the active monolith; identity service has no registration endpoint.
ActivationTransitionalIdentity supports active/disabled/locked state and email verification; administrative activation remains outside identity-service endpoints.
Password resetTransitional / Not implemented in identity serviceThe monolith has administrator reset operations. Identity has a reset-token entity but no reset endpoint.
Profile updateTransitionalThe monolith has user update operations. Identity service offers current-user retrieval but no profile-update endpoint.
Disable and reactivateTransitionalThe monolith exposes active-state administration. Identity stores disabled status but exposes no matching administration endpoint.
DeleteRequires confirmationNo confirmed identity-service user-delete endpoint or approved deletion lifecycle was found.

Technical implementation​

Identity users can be Active, Disabled, or Locked. Login accepts only active users. The model also records email-verification state, password-change requirement, last login, update time, tenant/employee linkage, and credential/security relationships.

Identity implements email-verification request and confirmation operations. The public distribution mechanism and production activation workflow are Requires confirmation. User creation, role assignment, administrative update, active-state changes, and password reset continue through monolith code paths during migration.

No deletion behavior is documented because neither a confirmed identity-service endpoint nor an approved retention/deletion policy is present in the reviewed source.

Confirmed source references​

  • microservices/src/identity-service/Domain/Entities/IdentityUser.cs
  • microservices/src/identity-service/Domain/Enums/IdentityUserStatus.cs
  • microservices/src/identity-service/Domain/Entities/PasswordResetToken.cs
  • microservices/src/identity-service/Domain/Entities/EmailVerificationToken.cs
  • microservices/src/identity-service/Program.cs
  • Controllers/AuthController.cs
  • Controllers/UserManagementController.cs
  • Controllers/SaasAdminController.cs

See Also​

Keywords​

  • Account state
  • User provisioning
  • Account deletion

Revision Information​

  • Last reviewed: 2026-07-14
  • Owner: identity-team
  • Status: Draft