> > Why is that ? .... I mean ... I have some SIP Phones that have no > > password configured, and the digest module is working fine, as they > > can get registered nicely. > > The server needs a clear-text password to do the digest > authentication. If it doesn't have a clear-text password, it > has no idea if the digest stuff it gets from the client is OK. > > I'm not sure what's going on in your setup, but I can > guarantee you that the digest code in FreeRADIUS requires > access to a clear-text password, and rejects the request if > it doesn't have one.
So you say that if I have a client returning, at authorize_check_query, a table with "User-Password" = "", it will not work for digest ?? and that it will only work if I return something like "User-Password" = "PASS" ?? > > When doing the query ( I'm using sql ) for > > authorize_check_query, the > > output table is returning a table with required fields, where > > Attribute "User-Password" = "". With this configuration it does not > > work. But, if I return Attribute "User-Password" = > > "MY_PASS" it works just perfect. > > That makes sense. A blank password isn't really a > password. It means you're not doing authentication at *all*. I got the point, but I'm telling you ... I have some clients that work with blank passwords and others that don't.... and just want to know why ... Regards, Lucas -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 10/05/2005 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
