Bump flask-appbuilder to 5.2.2 in FAB provider#69730
Open
potiuk wants to merge 1 commit into
Open
Conversation
Flask-AppBuilder 5.2.2 ships security-manager hardening — LDAP search-filter escaping, OAuth email-whitelist regex anchoring, and API-login provider validation. Airflow's vendored security manager already escapes LDAP filters (and validates the search filter), and it inherits the OAuth whitelist matching from FAB's OAuth view via super(), so these fixes land without any change to the vendored override; the FAB alignment test confirms the vendored code stays structurally in sync with the new release.
Contributor
|
Duplicate of #69706 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the vendored Flask-AppBuilder dependency in the FAB provider from 5.2.1 to 5.2.2.
FAB 5.2.2 hardens the security manager (LDAP search-filter escaping, OAuth email-allowlist regex anchoring, API-login provider validation). Airflow's vendored security manager already escapes LDAP filters (and validates the search filter), and it inherits the OAuth allowlist matching from FAB's OAuth view via
super().oauth_authorized(), sooverride.pyneeds no change;test_fab_alignment.pyconfirms the vendored code stays structurally in sync with 5.2.2.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines