ExternalPortalConfigRepository
Component Detail
Data Layer
medium complexity
backend
0
Dependencies
0
Dependents
2
Entities
0
Integrations
Description
Data access layer for persisting and retrieving external portal integration configurations, including endpoint URLs, encrypted authentication credentials, field mappings, and sync run history. Ensures credentials are stored securely and that configuration changes are auditable. Provides query methods used by both the sync service and the admin UI.
external-portal-config-repository
Sources & reasoning
Line 156 priority matrix assigns phase 2 to external portal coordination, mapping to v1.0. Line 115-116 identifies it as HLF-specific with explicit non-overlap requirements. Line 349 confirms its Fase 2 placement in the roadmap. MUST classification is HLF-scoped, not cross-org, so should_have at platform level.
-
docs/source/likeperson.md · line 115-116Koordinering med eget portalprosjekt: HLF redesigner «min side» på Dynamics-plattformen. Appen og portalen må ikke overlappe eller motarbeide hverandre.
-
docs/source/likeperson.md · line 349Koordinering med HLFs eksterne portalprosjekt
-
docs/source/likeperson.md · line 156Koordinering med ekstern portal | - | - | - | ✓ | ✓ | MUST (HLF) | 2
Responsibilities
- Persist and retrieve portal integration configuration records per organization
- Store authentication credentials with encryption at rest
- Manage field mapping definitions linking Meander fields to HLF portal fields
- Record sync run history with status, timestamps, and error payloads
- Enforce one active configuration per organization constraint
Interfaces
getConfig(organizationId: string): ExternalPortalConfig | null
saveConfig(config: ExternalPortalConfig): Promise<ExternalPortalConfig>
deleteConfig(configId: string): Promise<void>
saveSyncRun(run: SyncRun): Promise<SyncRun>
getSyncRuns(configId: string, limit: number): SyncRun[]
Related Data Entities (2)
Data entities managed by this component