Altinn/dialogporten

Restrict legal characters in text/plain content fields

Open

#2,427 opened on Jun 12, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (4 forks)auto 404
good first issue

Repository metrics

Stars
 (8 stars)
PR merge metrics
 (PR metrics pending)

Description

Introduction

We should restrict what characters can be used in Dialogporten to make it easier for service owners to detect errors

Description

See https://github.com/Altinn/dialogporten-frontend/issues/2219

Implementation

TBD

Tasks

  • Implementation tasks are added here
  • Prepare documentation (if relevant - either update working document, or add a new file in docs)
  • Add e2e-test (if relevant)

Threat Modelling

  • I have considered potential security risks (if risks were found, please list them below)

Acceptance criteria

GIVEN ... WHEN .... THEN ...

GIVEN ... WHEN .... THEN ...

Contributor guide

Research direction
Investigate the current character validation in Dialogporten's text/plain content fields and propose a restricted set of legal characters based on relevant standards (e.g., ASCII, Unicode categories) to minimize security risks and data inconsistency.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30