On 12 Jan 2015, at 21:34, mading087 <notifications@github.com> wrote:

It seems a good idea to support JWT as a new SIP authorization method. Wonder if anyone is interested? Think auth_db would be the best spot to add support for JWT.

Please check the work that is ongoing with OAuth - there is an IETF draft on that. /O

Thanks for the comments. Think a new module auth_jwt is a better way. Will take a closer look at auth_ephemeral. The two IETF draft I was looking at are http://www.ietf.org/id/draft-ietf-oauth-json-web-token-32.txt <http://www.ietf.org/id/draft-ietf-oauth-json-web-token-32.txt> and http://www.ietf.org/id/draft-ietf-jose-json-web-signature-40.txt <http://www.ietf.org/id/draft-ietf-jose-json-web-signature-40.txt>. OAuth 2.0 is a nice framework to handle auth and issue web tokens. But maybe the first step is to use configured public keys to verify the token and then use info from the token to validate SIP messages. Another thing is that it seems we need a new SIP header to send the JWT token. Cannot find an existing header that is suitable for JWT. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-69868305

I'd like to know the process to become a Kamailio developer so I can post the auth_jwt module for >review. Hope more experienced Kamailio developers can point out my errors and provide ideas for >enhancements.

You just have to fork and send a pull-request to get auth_jwt reviewed. No need to become KD for that. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-83054737

Just came back from Spring break. Thanks for the info. Some questions about module document and management interface. I was not sure if there is a common xml docbook tool, so I just made a text README file. Is this OK? Wonder if there is an xml tool I can use to convert the text file to xml docbook. I have read that the Kamailio MI interface is considered deprecated and should be supported only for backwards compatibility. New development should use RPC interface. Haven't written the management interface for the auth_jwt module, as I'm not sure if there are any guidelines on how to develop a RPC interface. Can someone point out such guidelines or an existing module with a good RPC interface implementation. Thanks --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-88120220

I am not aware of tools converting from text to docbook xml, maybe google can reveal some. The other way is the usual - write docbook files and then run: ``` make modules-readme modules=modules/auth_jwt ``` You need docbook tools/utils and xsl schemas installed. If not available for you, no problem, we can generate the readme and push to git repository. Writing in docbook is rather simple, you can easily see the format from other modules -- look into the doc/ subfolder of each module. You need the Makefile from there, updated to reflect the name of your module. The look at the modulename.xml for the base file for the docbook of the module. Besides the author info and some other details, this file includes other files, the most common being modulename_admin.xml . Thinking of a module that doesn't have large docbook and can be a good starting point: async Some other notes about docbook files: * http://www.kamailio.org/wiki/devel/module-docbook-readme Regarding the RPC, do you need to add such commands? Besides the link from Victor, check also the RPC API -- it might not be really up to date (maybe some new stuff missing), but what is there should be still valid: * http://www.kamailio.org/docs/docbooks/4.2.x/rpc_api/rpc_api.html --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-88128225

Thanks for letting me know. I'll try my best. Have to go through internal review process to get anything published. Just in case I cannot get this out in time, we can try the next release. This module will be constantly changed when we start to get feedback from field trials. On Thu, Apr 16, 2015 at 4:06 AM, Daniel-Constantin Mierla < notifications@github.com> wrote:

A short note to say that development for 4.3 will be frozen on April 22, next week Wednesday. If you want to get the module in the next major version, make a pull request by that time. Once the code is reviewed and is clean, you will get developer access to maintain the module.

— Reply to this email directly or view it on GitHub <https://github.com/kamailio/kamailio/issues/29#issuecomment-93685573>.

--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-93751931

Any update? --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-145562293

Closed #29. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#event-918059357

I am writing a JWT module now. I'll create a pull request when it's ready. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-284425599

Hi @poldon & @bwiles-vysk ! I am interested in your pull request status. Could you give a feeback about it ? Thanks -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-365214426

I didn’t as I left the company where I developed the code. Sent from my iPhone

On Oct 22, 2018, at 6:18 AM, Phil Lavin <notifications@github.com> wrote:

Did the source for this ever get published?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-431895774

Thanks. There seems to be interest as shown from the individual private implementation, but not enought to actually getting it into the Kamailio repository. If somebody wants to take this up, just let us know. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29#issuecomment-663585740