History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SMACK-224
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Matt Tucker
Reporter: Jay
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Smack

SASL Authenticate Mechanisim uses XMPP domain instead of FQDN

Created: 05/10/07 10:50 AM   Updated: 06/07/07 12:37 PM
Component/s: Core
Affects Version/s: 3.0.2
Fix Version/s: 3.0.4

Time Tracking:
Original Estimate: 30 minutes
Original Estimate - 30 minutes
Remaining Estimate: 30 minutes
Remaining Estimate - 30 minutes
Time Spent: Not Specified
Remaining Estimate - 30 minutes

Environment: Primarily will affect GSSAPI environments, but can affect any SASL authentication that requires the hostname.

Support Plan Customer Issue: No
Resolution Date: 06/07/07 12:37 PM
Acceptance Test - Add?: No


 Description  « Hide
When performing SASL authentication, the SASLAuthentication object uses XMPPConnection.getServiceName() to supply to the SASLMechanisim.authenticate(user,host,pass) method (line 192). When using GSSAPI, the fully qualified domain name (FQDN) of the server is required for authentication. For servers where the FQDN of the server does not match the domain, authentication will fail.

This is related in nature to JM-952

Simple fix: Change to connection.getHost().



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Matt Tucker - 05/10/07 12:54 PM
Hmm. Is this correct for other SASL mechanisms??

Matt Tucker - 06/07/07 11:20 AM
Crap, it looks like we broke Google Talk, and possibly other domains that use DNS SRV records?

Matt Tucker - 06/07/07 11:21 AM

Matt Tucker - 06/07/07 12:37 PM
Closing this one again based on fix and testing by Jay. We can rep-open again later if there are any problems.