Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lemonldap-ng lemonldap-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 314
    • Issues 314
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LemonLDAP NGLemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #2295
Closed
Open
Issue created Aug 25, 2020 by Maxime Besson@maxbes🔧Maintainer

Erroneous use of NTLM should be explicitely reported to the user

As seen in #2294 (closed) , misconfiguration of Windows clients are likely to lead to NTLM being attempted against LLNG when Kerberos auth is used.

The current error message might lead users to believe there is an issue with the server-side of things. We need a more explicit error message.

NTLM tickets are easy enough to spot:

00000000  4e 54 4c 4d 53 53 50 00  01 00 00 00 97 82 08 e2  |NTLMSSP.........|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  0a 00 ba 47 00 00 00 0f                           |...G....|
00000028
Edited Aug 25, 2020 by Maxime Besson
Assignee
Assign to
Time tracking