Skip to content

web/admin: fix display bug for assigned users in application bindings in the wizard (cherry-pick #13435)#13452

Merged
BeryJu merged 1 commit intoversion-2025.2from
cherry-pick-7357f0-version-2025.2
Mar 11, 2025
Merged

web/admin: fix display bug for assigned users in application bindings in the wizard (cherry-pick #13435)#13452
BeryJu merged 1 commit intoversion-2025.2from
cherry-pick-7357f0-version-2025.2

Conversation

@gcp-cherry-pick-bot
Copy link
Contributor

Cherry-picked web/admin: fix display bug for assigned users in application bindings in the wizard (#13435)

  • web: Add InvalidationFlow to Radius Provider dialogues

What

  • Bugfix: adds the InvalidationFlow to the Radius Provider dialogues
    • Repairs: {"invalidation_flow":["This field is required."]} message, which was not propagated
      to the Notification.
  • Nitpick: Pretties ?foo=${true} expressions: s/\?([^=]+)=\$\{true\}/\1/

Note

Yes, I know I'm going to have to do more magic when we harmonize the forms, and no, I didn't add the
Property Mappings to the wizard, and yes, I know I'm going to have pain with the new version of
the wizard. But this is a serious bug; you can't make Radius servers with either of the current
dialogues at the moment.

  • This (temporary) change is needed to prevent the unit tests from failing.

# What

# Why

# How

# Designs

# Test Steps

# Other Notes

  • Revert "This (temporary) change is needed to prevent the unit tests from failing."

This reverts commit dddde09.

  • web/admin: fix display bug for assigned users in application bindings in the wizard

What

Modifies the type-of-binding detection algorithm to check if there's a user field and
that it's a number.

Why

The original type-of-binding detector checked if the field was set and asserted that it was a string
of at least one character. Unfortunately, this doesn't work for user, where the primary key is an
integer. Changing the algorithm to "It's really a string with something in it, or it's a number,"
works.

Testing

  • Ensure you have at least one user you can use, and that user has a username.
  • Navigate through the Application Wizard until you reach the binding page.
  • Create a user binding
  • See that the user shows up in the table.

… in the wizard (#13435)

* web: Add InvalidationFlow to Radius Provider dialogues

## What

- Bugfix: adds the InvalidationFlow to the Radius Provider dialogues
  - Repairs: `{"invalidation_flow":["This field is required."]}` message, which was *not* propagated
    to the Notification.
- Nitpick: Pretties `?foo=${true}` expressions: `s/\?([^=]+)=\$\{true\}/\1/`

## Note

Yes, I know I'm going to have to do more magic when we harmonize the forms, and no, I didn't add the
Property Mappings to the wizard, and yes, I know I'm going to have pain with the *new* version of
the wizard. But this is a serious bug; you can't make Radius servers with *either* of the current
dialogues at the moment.

* This (temporary) change is needed to prevent the unit tests from failing.

\# What

\# Why

\# How

\# Designs

\# Test Steps

\# Other Notes

* Revert "This (temporary) change is needed to prevent the unit tests from failing."

This reverts commit dddde09.

* web/admin: fix display bug for assigned users in application bindings in the wizard

## What

Modifies the type-of-binding detection algorithm to check if there's a user field and
that it's a number.

## Why

The original type-of-binding detector checked if the field was set and asserted that it was a string
of at least one character. Unfortunately, this doesn't work for `user`, where the primary key is an
integer. Changing the algorithm to "It's really a string with something in it, *or* it's a number,"
works.

## Testing

- Ensure you have at least one user you can use, and that user has a username.
- Navigate through the Application Wizard until you reach the binding page.
- Create a user binding
- See that the user shows up in the table.
@gcp-cherry-pick-bot gcp-cherry-pick-bot bot requested a review from a team as a code owner March 10, 2025 15:34
@netlify
Copy link

netlify bot commented Mar 10, 2025

Deploy Preview for authentik-docs ready!

Name Link
🔨 Latest commit 530b189
🔍 Latest deploy log https://app.netlify.com/sites/authentik-docs/deploys/67cf069379c3ff00080ad399
😎 Deploy Preview https://deploy-preview-13452--authentik-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@codecov
Copy link

codecov bot commented Mar 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.76%. Comparing base (35c739e) to head (530b189).
Report is 1 commits behind head on version-2025.2.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@               Coverage Diff               @@
##           version-2025.2   #13452   +/-   ##
===============================================
  Coverage           92.75%   92.76%           
===============================================
  Files                 793      793           
  Lines               40285    40285           
===============================================
+ Hits                37367    37370    +3     
+ Misses               2918     2915    -3     
Flag Coverage Δ
e2e 48.10% <ø> (+<0.01%) ⬆️
integration 24.09% <ø> (ø)
unit 90.46% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@BeryJu BeryJu merged commit a5ee159 into version-2025.2 Mar 11, 2025
80 of 85 checks passed
@BeryJu BeryJu deleted the cherry-pick-7357f0-version-2025.2 branch March 11, 2025 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants