Project

General

Profile

Actions

Bug #26939

open

User management UI does not display when a user info is a complex JSON object

Added by Clark ANDRIANASOLO 8 days ago. Updated 3 days ago.

Status:
Pending release
Priority:
1 (highest)
Category:
Web - UI & UX
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
First impressions of Rudder
Effort required:
Small
Priority:
139
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When updating a user information in the user management API, in the field otherInfo, if the values are JSON but are not string (int, null, object), the API will accept the update.

But when opening the user management page, there is a text Waiting for server response, and there is a notification error, and some network requests in the browser network tools are aborted.

This is due to specifically decoding strings in the otherInfo field in the Elm app, and it seems to fail silently, without an explicit decoding error.

We should be able at least to display the custom information in the user management UI, even if the format of values is not supported for edit (we don't know yet how to edit ints, and JSON objects).

Workaround is to update the user information data with string values.


Files

clipboard-202505271512-xob8k.png (136 KB) clipboard-202505271512-xob8k.png François ARMAND, 2025-05-27 15:12
Actions #1

Updated by François ARMAND 8 days ago

  • Priority changed from To review to 1 (highest)
Actions #2

Updated by Clark ANDRIANASOLO 8 days ago

  • Status changed from New to In progress
Actions #3

Updated by Clark ANDRIANASOLO 8 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to Raphael GAUTHIER
  • Pull Request set to https://github.com/Normation/rudder/pull/6390
Actions #4

Updated by Clark ANDRIANASOLO 7 days ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by François ARMAND 3 days ago

Works as expected: now the unknonwn field is displayed without breaking anything

Actions

Also available in: Atom PDF