bugMicrosoft NTLM authentication library - Bugs: bug #45089, Problem with cross domain...

 
 

bug #45089: Problem with cross domain authentication

Submitted by:  None
Submitted on:  Tue 12 May 2015 09:40:01 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 12 May 2015 09:40:01 PM UTC, original submission:

When the client is on Domain A, and is requesting a resource on Domain B, and Domain A and B have a mutual trust relationship, we can get an authentication failure.

This happens if you build the response and specify a username without @domain in it.

libntlm sees that there is no @ symbol, so it tries to base the domain off the domain stored in the challenge. But the challenge holds the domain of the resource, rather than the client. So when building the response, the client gets mis-identified and the response fails.

A workaround is to always use the user@domain syntax when specifying the user for the response.

One way to solve this is to add a new method for building the response that lets you supply the client domain.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

No Changes Have Been Made to This Item

Back to the top


Powered by Savane 3.1-cleanup1