[reSIProcate] ServerRegistration with external authorization

[Scott Godin]

You will want to override the ServerAuthManager class in order to
provide external authorization.

Scott

> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-
> devel-bounces at list.sipfoundry.org] On Behalf Of Valentin Nechayev
> Sent: Monday, May 08, 2006 8:12 AM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] ServerRegistration with external authorization
> 
> Hi,
> we need to use external authorization and store for a registrar.
> Currently (I study revision 6182) resiprocate has
> resip/dum/ServerRegistration which doesn't allow this because
> tries to handle registration internally. Persistence manager can't
> help because it gets only AORs but not original request (it's
> nesessary to bind AOR to registered account), nor
> ServerRegistrationHandler.
> 
> It's not problem to replace ServerRegistration with custom class,
> but to separate library and application properly it seems better
> to give some mechanism to make runtime override, e.g. via
> AppDialogSet and pass makeServerRegistration() to its. Is there
> any recommended way to do it, or even some future revision will
> contain this option?
> 
> Or I missed some another mechanism to do this?
> 
> --
> Valentin Nechayev
> PortaOne Inc., Software Engineer
> mailto:netch at portaone.com
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel