On 5/5/06, Kai Vehmanen <[EMAIL PROTECTED]> wrote:
hmm, it seems that if stack ends up selecting OPTIONS as the keep-alive mechanism, but the proxy challenges the OPTIONS, the stack does not quite work right -> the 407 is never delivered to the client which could authorize it (that's my guess, could be something else of course). If I try plain ol' OPTIONS (not related to keep-alive), I get the challenge and can handle it with nua_auth().
My idea was to re-use the usename and password used in REGISTER request. While the keepalive OPTTIONS is just a hack, I think STUN with rfc3489bis uses digest authenticatio, too. Now the problem is that there is no single nua event which application could use to prompt authentication from user.
How's this suppose to work?
REGISTER is challenged with a certain realm and the application provides NUA with username and password for the realm.The keepalive OPTIONS uses the same username and password if it is challenged using the same realm. The above is the theory, but the code has never been tested. Caveat emptor. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
