Project

General

Profile

Actions

Bug #25299

closed

User management 'providers' column is still missing when there are multiple values

Added by Clark ANDRIANASOLO 4 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
I hate Rudder for that
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
110
Name check:
To do
Fix check:
To do
Regression:
No

Description

After starting Rudder with the auth-backends plugin to create OIDC users (properties rudder.auth.provider=oidc,file and the configuration for OIDC), in the user management interface the 'providers' column allows to differentiate users provided by OIDC or file, or both.

But when disabling OIDC (properties rudder.auth.provider=file), all users provided by OIDC are still listed in the user management interface, and the 'providers' column is missing. We have to open the user detail to know that they are managed by OIDC, and there is no explicit warning that the user will not be able to log in.

When there are users with provider other than "file", the providers column should still be displayed. And we should add a warning for users that will not be able to log in because of their provider being not enabled in Rudder from the rudder.auth.provider property.

Actions #1

Updated by Clark ANDRIANASOLO 4 months ago

  • Status changed from New to In progress
Actions #2

Updated by Clark ANDRIANASOLO 4 months 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/5823
Actions #3

Updated by Clark ANDRIANASOLO 4 months ago

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

Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released
  • Priority changed from 55 to 110

This bug has been fixed in Rudder 8.2.0~beta1 which was released today.

Actions

Also available in: Atom PDF