Hi,

Sorry for the late reply to this issue. After some investigation we think there might not be such a strong need for the patch as we don't see real use cases.
We'll drop the patch.

Thank you,
Lucian


On 08/05/2014 11:31 AM, Alekzander Spiridonov wrote:
That's for sure a rare case. So I'd prefer it not to be a default behavior.

BTW, any example of real use-case?


2014-08-04 18:08 GMT+04:00 Daniel-Constantin Mierla <miconda@gmail.com>:
Hello,

it could be useful in various cases, when the password is wrong, the credentials to be available in config.

What I would like to discuss a bit further is whether this should be made a module parameter or not. Database query is done anyhow, so the extra processing is only pushing credentials values in avps when password was wrong.

Thinking of how I use the credentials so far, I won't be affected by this change. Other opinions?

Cheers,
Daniel


On 30/07/14 17:39, Lucian Balaceanu wrote:
Hi,

At 1&1, we found it useful to trigger the generation of AVPs even if authentication fails. Do you find such a facility useful for upstream?
The changes are really small as you can see from the attached patch.

Thank you,
Lucian Balaceanu


_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev




--
Best regards,
Alekzander Spiridonov

_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev