Implement Procative Authorization

[johnmanning72]

No description provided.

[jmillan]

Thanks @johnmanning72,

I'll review it in detail in the following days.

I'll most probably do some modifications to comply with the repository format and usage.

Thanks!

[jmillan]

NOTE 1: Since there is a single key in the auth map it makes no sense for it to be a map.

Also, @johnmanning72 , does this work only for REGISTER? Does it work for subsequent N REGISTER without being challenged? Does it also work for INVITE and other methods?

NOTE 2: I'll need to prepare real environment before merging this, so it wont be immediate.

[johnmanning72]

Re: Note 1: Agreed, there is no need for it to be a map if an application only registers with a a single registrar. A map is more flexible though as it supports multiple registrar servers simultaneously.

Also, the code is currently configured to include the Auth header in all outgoing requests. If this is a problem, it would be easy to limit it to just REGISTER or INVITE messages.

The Auth header will continue to be sent in all messages until the Server challenges it by responding with a '401 Unauthorized'. Our own server implementation will do this after every 10 REGISTER/INVITEs