Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

24462-reduce_ldap_queries_for_lfs.yml

  • Drew Blessing's avatar
    29414ab0
    Reduce hits to LDAP on Git HTTP auth by reordering auth mechanisms · 29414ab0
    Drew Blessing authored
    We accept half a dozen different authentication mechanisms for
    Git over HTTP. Fairly high in the list we were checking user
    password, which would also query LDAP. In the case of LFS,
    OAuth tokens or personal access tokens, we were unnecessarily
    hitting LDAP when the authentication will not succeed. This
    was causing some LDAP/AD systems to lock the account. Now,
    user password authentication is the last mechanism tried since
    it's the most expensive.
    29414ab0
    History
    Reduce hits to LDAP on Git HTTP auth by reordering auth mechanisms
    Drew Blessing authored
    We accept half a dozen different authentication mechanisms for
    Git over HTTP. Fairly high in the list we were checking user
    password, which would also query LDAP. In the case of LFS,
    OAuth tokens or personal access tokens, we were unnecessarily
    hitting LDAP when the authentication will not succeed. This
    was causing some LDAP/AD systems to lock the account. Now,
    user password authentication is the last mechanism tried since
    it's the most expensive.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.