Hi Tony,
I think the following will lead to resolution of your case.
There is 2 rounds of I/O between client and server during authentication.
During the first round the client learns what the server is expecting.
During the second round client sends the actual values and the server
performs the actual authentication. During the first round the value of
password in NULL, which is logical and it is probably your case. As for the
solution:
You should check the value during JPACKET__SET subtype and not the
JPACKET__GET which is the first round. Use this if statement to check the
round of negotiation (which is the packet subtype).
if (jpacket_subtype(m->packet) == JPACKET__SET)
hope this helps
zad
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Tony Byers
> Sent: Friday, May 11, 2001 9:43 PM
> To: [EMAIL PROTECTED]
> Subject: [JDEV] passwords
>
>
> Hello -
>
> I thought I had this figured out but I don't. Does anyone know how to
> obtain the password from the client in any of the mod_auth files. I've
> stuck the following line in many different places and password is always
> NULL.
>
> password = xmlnode_get_tag_data(m->packet->iq, "password");
>
> I've commented out mod_auth_digest and mod_auth_0k in jabber.xml so I'm
> assuming that password verification must be done in mod_auth_plain_jane.
>
> Any information about the client password would be great. I'm totally
> lost at this point.
>
> Tony Byers
>
> ___________________________________________________________________
> To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax,
> all in one place - sign up today at http://www.zdnetonebox.com
>
> _______________________________________________
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
