<br><div class="gmail_quote">On Mon, Aug 2, 2010 at 12:48 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Takeshi,<br>
<br>
The tutorial was written for the case where you provide the plain-text<br>
password and the auth engine calculates the ha1.<br>
<br>
If you want to disable the HA1 calculation, in that case you need to<br>
cache it and to provide it to auth engine via the password AVP (for pv<br>
authentication).<br>
<br>
Actually, aside of changing the "calculate_ha1" param , you should not<br>
change anything else - if your changes are consistent (like adding in<br>
"password" column in DB the HA1 value), the caching mechanism will work<br>
unchanged - it will load, cache and provide the HA1 instead of passwd.<br></blockquote></div><br>But Bogdan, it might not happen that www/proxy_authorize would need to use the password from column ha1b instead (username in credentials containing "@domain")?<br>
<br>So If that happens, next time when I get the password from cache, it will not work. <br>Am I missing something? <br><br>br,<br>takeshi<br><br>