Does api-key PR been merged on v6.1.0 release? https://github.com/apache/superset/pull/37973

[cw1427]

#37973
Found this PR got merged, but when upgradae to lates v6.1.0 which could not enable the api-key feature with config added:

FAB_API_KEY_ENABLED = True
FAB_API_KEY_PREFIXES = ["sst_"]
FEATURE_FLAGS={
"FAB_API_KEY_ENABLED": True
}

[dosubot[bot]]

Hi @cw1427! I'm Dosu and I'm helping the Apache Superset team.

PR #37973 was merged on March 24, 2026 into the main branch [1]. Your configuration looks correct, but there are a few additional requirements that may explain why it's not working:

1. Flask-AppBuilder version must be ≥ 5.2.0

The API key feature relies on FAB 5.2.0+. Verify inside your environment:

pip show flask-appbuilder

If the version is too old, the UI panel simply won't appear [2].

2. Run database migrations

The ab_api_key table must be created after enabling the config:

superset db upgrade
superset init

3. Critical bug fix in PR #39437

A bug was fixed (merged April 2026) where API key authentication silently failed due to a wrong method name. Make sure your build includes this fix — without it, even if the UI works, authentication with API keys will fail [2].

4. Confirm both config values are set

You need both the backend config AND the feature flag (which you appear to have):

FAB_API_KEY_ENABLED = True
FAB_API_KEY_PREFIXES = ["sst_"]

FEATURE_FLAGS = {
    "FAB_API_KEY_ENABLED": True,
}

The API Keys section should appear on the User Info page (/user_info/). If it still doesn't show up after confirming the above, could you share the output of pip show flask-appbuilder and confirm you've run superset db upgrade?

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.