[Feature flag] Cleanup of allow_ldap_users_to_authenticate_with_gitlab_username

Summary

This issue is to cleanup the allow_ldap_users_to_authenticate_with_gitlab_username feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

MR: !186848 (merged)

Issue: #215357 (closed)

Owners

  • Team: groupauthentication
  • Most appropriate slack channel to reach out to: ##g_sscs_authentication
  • Best individual to reach out to: @bdenkovych
  • PM: NAME

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

  • Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
  • Create a merge request to remove allow_ldap_users_to_authenticate_with_gitlab_username feature flag. Ask for review and merge it.
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
    • Create a changelog entry.
  • Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
    • /chatops run auto_deploy status d556810b72fae953ed333251102c869dff7442d6
  • Close the feature issue to indicate the feature will be released in the current milestone.
  • If not already done, clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete allow_ldap_users_to_authenticate_with_gitlab_username --dev --pre --staging --staging-ref --production
  • Close this rollout issue.
Edited Jun 06, 2025 by Bogdan Denkovych
Assignee Loading
Time tracking Loading