You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
gitea-fork-majority-judgment/vendor/github.com/Azure/go-ntlmssp
6543 e374bb7e2d
[Vendor] Update go-ldap to v3.2.4 (#13163)
4 years ago
..
.travis.yml [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
LICENSE [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
README.md [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
authenticate_message.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
authheader.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
avids.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
challenge_message.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
messageheader.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
negotiate_flags.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
negotiate_message.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
negotiator.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
nlmp.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
unicode.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
varfield.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago
version.go [Vendor] Update go-ldap to v3.2.4 (#13163) 4 years ago

README.md

go-ntlmssp

Golang package that provides NTLM/Negotiate authentication over HTTP

GoDoc Build Status

Protocol details from https://msdn.microsoft.com/en-us/library/cc236621.aspx Implementation hints from http://davenport.sourceforge.net/ntlm.html

This package only implements authentication, no key exchange or encryption. It only supports Unicode (UTF16LE) encoding of protocol strings, no OEM encoding. This package implements NTLMv2.

Usage

url, user, password := "http://www.example.com/secrets", "robpike", "pw123"
client := &http.Client{
  Transport: ntlmssp.Negotiator{
    RoundTripper:&http.Transport{},
  },
}

req, _ := http.NewRequest("GET", url, nil)
req.SetBasicAuth(user, password)
res, _ := client.Do(req)

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.