Skip to content

Implement Procative Authorization#965

Open
johnmanning72 wants to merge 2 commits intoversatica:masterfrom
johnmanning72:Proactive_Authorization_On_Registers
Open

Implement Procative Authorization#965
johnmanning72 wants to merge 2 commits intoversatica:masterfrom
johnmanning72:Proactive_Authorization_On_Registers

Conversation

@johnmanning72
Copy link

No description provided.

@jmillan
Copy link
Member

jmillan commented Feb 19, 2026

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
Copy link
Member

jmillan commented Feb 23, 2026

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
Copy link
Author

johnmanning72 commented Feb 25, 2026

Re: Note 1: Agreed, there is no need for it to be a map.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants