I have a new system using its own domain and the hostname is NOT the
sipdomain name.

After comparing a spark login (debug log)---

2012.01.27 14:25:08 execute: ->
2012.01.27 14:25:08 execute: Request performed successfully
2012.01.27 14:25:08 execute: <-
2012.01.27 14:25:13 NIOConnection: startTLS: using c2s
2012.01.27 14:25:14 SASLAuthentication: SaslException
javax.security.sasl.SaslException: DIGEST-MD5: digest response format
violation. Nonexistent realm: voice.myitdepartment.net
at 
com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:430)
at 
com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:244)
at 
org.jivesoftware.openfire.net.SASLAuthentication.handle(SASLAuthentication.java:296)
at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:165)
at 
org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandler.java:133)
at 
org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:570)
at 
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at 
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at 
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at 
org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at 
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at 
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at 
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at 
org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:58)
at 
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:185)
at 
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at 
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at 
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at 
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:239)
at 
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:283)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at 
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)
at java.lang.Thread.run(Thread.java:636)

When I use pidgin, it says no realm used, and it logs in fine.


2012.01.27 14:38:08 execute: ->
2012.01.27 14:38:08 execute: Request performed successfully
2012.01.27 14:38:08 execute: <-
2012.01.27 14:38:09 NIOConnection: startTLS: using c2s
2012.01.27 14:38:10 000137 (01/03/00) - Connection #1 tested: OK
2012.01.27 14:38:10 000138 (01/03/00) - Connection #1 tested: OK
2012.01.27 14:38:10 AuthorizationManager: Trying Default
Mapping.map(xxreplaced_was sip users idxx)
2012.01.27 14:38:10 DefaultAuthorizationMapping: No realm found
2012.01.27 14:38:10 AuthorizationManager: Trying Default
Policy.authorize(xxreplaced_was sip users idxx , xxwas passwordxx)
2012.01.27 14:38:10 DefaultAuthorizationPolicy: Checking authenID realm
2012.01.27 14:38:10 000138 (01/03/00) - Connection #3 tested: OK
2012.01.27 14:38:10 000139 (01/03/00) - Connection #3 tested: OK
2012.01.27 14:38:10 000139 (01/03/00) - Connection #2 tested: OK
2012.01.27 14:38:10 000140 (01/03/00) - Connection #2 tested: OK
2012.01.27 14:38:10 000140 (01/03/00) - Connection #1 tested: OK
2012.01.27 14:38:10 000141 (02/03/00) - Connection #3 tested: OK
2012.01.27 14:38:10 000142 (02/03/00) - #1 registered a statement as
closed which wasn't known to be open. This could happen if you close a
statement twice.
2012.01.27 14:38:10 000142 (02/03/00) - Connection #1 tested: OK
2012.01.27 14:38:10 000142 (01/03/00) - Connection #3 tested: OK

So does this mean there is a basic issue with SASL (I am thinking the
answer is here because of the "violation".

javax.security.sasl.SaslException: DIGEST-MD5: digest response format
violation. Nonexistent realm:mysipdomain.tld

I am also thinking that sasl.mechs, sasl.realms and
sasl.approvedRealms is set by sipxconfig, correct? If so, it would be
a configuration issue.

Am I daft?

-- 
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!

-- 
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to