Openfire (ARCHIVED)

PLAIN SASL authentication fails to authenticate clients that are sending bare JIDs

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.2.0
  • Fix Version/s: 3.2.1
  • Component/s: Core
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

"We just ran into a problem doing Authentication withWildFire using the Open Source SoapBox Framework and SASL Plain.

The SoapBox Framework is using a bare JID ("user@server")as the authid that's passed across the link. The Jive server is expectingonly a user name ("user").

The RFC doesn't really say either way, and I figurethis is a good chance to get it clarified.

(The SoapBox Framework now can do both, but I would sureprefer just one or the other)

--Chris Mullins"

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: