Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NTLM type1msg not getting expected response #131

Open
powercat92 opened this issue Nov 15, 2023 · 0 comments
Open

NTLM type1msg not getting expected response #131

powercat92 opened this issue Nov 15, 2023 · 0 comments

Comments

@powercat92
Copy link

Hello there. Using Node-SP-Auth, it seems that when I get the response to type1msg, I do not get the 'www-authenticate' hash. The value of that header is simply 'NTLM'. From everything I can determine, the module is submitting the correct headers to my 2013 On-prem SP site (type1msg hash, URL, options all look correct). I have the same site working using httpNTLM module and using that module I do get NTLM [hash] in 'www-authenticate' response. I do not get any errors, the request gets sent, the type1msg response gets returned and it just hangs there.

0|source | 401
0|source | { 'content-type': 'text/plain; charset=utf-8',
0|source | server: 'Microsoft-IIS/8.5',
0|source | sprequestguid: '3766eea0-7438-5046-3aa5-c6a419ae8ac2',
0|source | 'request-id': '3766eea0-7438-5046-3aa5-c6a419ae8ac2',
0|source | 'x-frame-options': 'SAMEORIGIN',
0|source | sprequestduration: '4',
0|source | spiislatency: '0',
0|source | 'www-authenticate': 'NTLM',
0|source | 'x-powered-by': 'ASP.NET',
0|source | microsoftsharepointteamservices: '15.0.0.4701',
0|source | 'x-content-type-options': 'nosniff',
0|source | 'x-ms-invokeapp': '1; RequireReadOnly',
0|source | date: 'Wed, 15 Nov 2023 18:20:30 GMT',
0|source | connection: 'close',
0|source | 'content-length': '16' }
0|source | 401 UNAUTHORIZED

My primary goal here is to use node-sp-auth for AD login, but since I already have NTLM working I am trying to verify that I have the module configured correctly before working on AD login. Once I have it working with NTLM, I'll be certain that the module is set up and working in my environment.

Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant