[sip-comm-dev] How does SC do authentication?


#1

Grep tells me that headerFactory.createAuthorizationHeader() in only called in
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager. I put printlines and debugger breakpoints in there, but when I run SC it seems that that code is never entered, yet wireshark is telling me that SC is successfully authenticating. So how is it doing it?

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hey Joseph,

That's exactly where it happens. How did you run the application when
you were looking for your println-s?

We disable System.out output in windows and linux installation packages.

You should see them when running from source though.

Cheers
Emil

Joseph Shraibman wrote:

···

Grep tells me that headerFactory.createAuthorizationHeader() in only
called in
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.
  I put printlines and debugger breakpoints in there, but when I run SC
it seems that that code is never entered, yet wireshark is telling me
that SC is successfully authenticating. So how is it doing it?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Emil Ivov wrote:

Hey Joseph,

That's exactly where it happens. How did you run the application when
you were looking for your println-s?

First by just compiling it and running it, and then in NetBeans. I added both printlns and a logger.warning()

We disable System.out output in windows and linux installation packages.

You should see them when running from source though.

Should System.err work?

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Nevermind, I thought I had the "compile on save" turned on, but I didn't, so my printlines were never compiled in.

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Note that even if you did, SIP Communicator needs to bundle all the code
into OSGi bundles in addition to only compiling it. This is how it
actually executes. The whole build process takes about a minute
(depending on the machine you are on) so if you don't experience it in a
noticeable way then you are probably not running your modifications.

Hope this helps
Emil

Joseph Shraibman wrote:

···

Nevermind, I thought I had the "compile on save" turned on, but I
didn't, so my printlines were never compiled in.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net