Hello,
the "new in Kamailio 5.5.x" document has been updated. Again, a really impressive set of changes that lead to this release:
Over 1350 commits have been done in the last development period from over 70 individual contributors.
You find the document at the usual place in our wiki: https://www.kamailio.org/wiki/features/new-in-5.5.x
Many thanks to everybody who contributed to Kamailio.
Help in updating the documentation (e.g. core cookbook, pseudo-variable and transformation section) in the wiki is really welcome, as some content is probably still missing there.
Best regards,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
Module: kamailio
Branch: master
Commit: 26e3adfd0af949cf6e611798ad02506d927a8c8f
URL: https://github.com/kamailio/kamailio/commit/26e3adfd0af949cf6e611798ad02506…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-05-03T08:01:12+02:00
modules: readme files regenerated - jwt ... [skip ci]
---
Modified: src/modules/jwt/README
---
Diff: https://github.com/kamailio/kamailio/commit/26e3adfd0af949cf6e611798ad02506…
Patch: https://github.com/kamailio/kamailio/commit/26e3adfd0af949cf6e611798ad02506…
---
diff --git a/src/modules/jwt/README b/src/modules/jwt/README
index 7a7400a4b1..459f10a822 100644
--- a/src/modules/jwt/README
+++ b/src/modules/jwt/README
@@ -122,14 +122,17 @@ modparam("jwt", "key_mode", 1)
libjwt (e.g., RS256, HS256, ES256, ...)
* claims - the list of claims to be added to JWT, in the format
"name1=value1;name2=value2;..." (same as the SIP parameters
- format).
+ format). The string values can be enclosed in single or double
+ quotes. If a value is not eclosed in between quotes, it is added as
+ numeric value if it is successfully converted to a long value,
+ otherwise is added as string value.
This function can be used from ANY_ROUTE.
Example 1.2. jwt_generate usage
...
jwt_generate("/path/to/prvkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci");
+ "caller='$fU';callee='$tU';callid='$ci';index=100");
...
4.2. jwt_verify(pubkey, alg, claims, jwtval)
@@ -142,7 +145,8 @@ modparam("jwt", "key_mode", 1)
libjwt (e.g., RS256, HS256, ES256, ...)
* claims - the list of claims to be checked they are in the JWT, in
the format "name1=value1;name2=value2;..." (same as the SIP
- parameters format).
+ parameters format, see also the description of claims parameter for
+ jwt_generate()).
* jwtval - the value of the JWT to verify
This function can be used from ANY_ROUTE.
@@ -150,7 +154,7 @@ modparam("jwt", "key_mode", 1)
Example 1.3. jwt_verify usage
...
if(!jwt_verify("/path/to/pubkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci",
+ "caller='$fU';callee='$tU';callid='$ci';index=100",
"$var(jwt)") {
xwarn("failed to verify jwt\n");
}
@@ -171,6 +175,6 @@ modparam("jwt", "key_mode", 1)
Example 1.4. $jwt(name) usage
...
jwt_generate("/path/to/prvkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci");
+ "caller='$fU';callee='$tU';callid='$ci';index=100");
xinfo("jwt is: $jwt(val)");
...
Module: kamailio
Branch: master
Commit: 7d24a7afe02bf1f7c8ddddfcfc9f1c287296c996
URL: https://github.com/kamailio/kamailio/commit/7d24a7afe02bf1f7c8ddddfcfc9f1c2…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-05-03T08:00:32+02:00
jwt: more details about claims parameter format
---
Modified: src/modules/jwt/doc/jwt_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/7d24a7afe02bf1f7c8ddddfcfc9f1c2…
Patch: https://github.com/kamailio/kamailio/commit/7d24a7afe02bf1f7c8ddddfcfc9f1c2…
---
diff --git a/src/modules/jwt/doc/jwt_admin.xml b/src/modules/jwt/doc/jwt_admin.xml
index dba928b523..36d3d0d0f7 100644
--- a/src/modules/jwt/doc/jwt_admin.xml
+++ b/src/modules/jwt/doc/jwt_admin.xml
@@ -109,6 +109,10 @@ modparam("jwt", "key_mode", 1)
<para>
claims - the list of claims to be added to JWT, in the format
"name1=value1;name2=value2;..." (same as the SIP parameters format).
+ The string values can be enclosed in single or double quotes. If a
+ value is not eclosed in between quotes, it is added as numeric
+ value if it is successfully converted to a long value, otherwise is
+ added as string value.
</para>
</listitem>
</itemizedlist>
@@ -120,7 +124,7 @@ modparam("jwt", "key_mode", 1)
<programlisting format="linespecific">
...
jwt_generate("/path/to/prvkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci");
+ "caller='$fU';callee='$tU';callid='$ci';index=100");
...
</programlisting>
</example>
@@ -151,7 +155,8 @@ modparam("jwt", "key_mode", 1)
<listitem>
<para>
claims - the list of claims to be checked they are in the JWT, in the format
- "name1=value1;name2=value2;..." (same as the SIP parameters format).
+ "name1=value1;name2=value2;..." (same as the SIP parameters format,
+ see also the description of claims parameter for jwt_generate()).
</para>
</listitem>
<listitem>
@@ -168,7 +173,7 @@ modparam("jwt", "key_mode", 1)
<programlisting format="linespecific">
...
if(!jwt_verify("/path/to/pubkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci",
+ "caller='$fU';callee='$tU';callid='$ci';index=100",
"$var(jwt)") {
xwarn("failed to verify jwt\n");
}
@@ -206,7 +211,7 @@ modparam("jwt", "key_mode", 1)
<programlisting format="linespecific">
...
jwt_generate("/path/to/prvkey.pem", "RS256",
- "caller=$fU;callee=$tU;callid=$ci");
+ "caller='$fU';callee='$tU';callid='$ci';index=100");
xinfo("jwt is: $jwt(val)");
...
</programlisting>
Daniel,
I studied a bit topos_redis source and noticed that it lacks x_context
td and tt keys.
Is there something else missing in order to make spirals work also when
redis backend is in use?
-- Juha
Hello,
the formal notification that the development for the next major version
5.5.0 is now frozen. The focus has to be on testing the master branch.
Also, the master branch should not get commits with new features till
the branch 5.5 is created, expected to happen in 2-4 weeks, a matter of
how testing goes on. Meanwhile, the commits with new features in the C
code can be pushed to personal branches, new pull requests can still be
done, but they will be merged after branching 5.5.
Can still be done commits with documentation improvements, enhancements
to related tools (e.g., kamctl, kamcmd), merging exiting pull requests
at this
moment, exporting missing KEMI functions and completing the functionality
of the new modules added in 5.5.
Once the branch 5.5 is created, new features can be pushed again to
master branch as usual. From that moment, the v5.5.0 should be out very
soon, time used for further testing but also preparing the release of
packages.
If someone is not sure if a commit brings a new feature, just make a
pull request and it can be discussed there on github portal or via
sr-dev mailing list.
A summary of what is new in upcoming 5.5 is going to be built at:
 * https://www.kamailio.org/wiki/features/new-in-5.5.x
Upgrade guidelines will be collected at:
 * https://www.kamailio.org/wiki/install/upgrade/5.4.x-to-5.5.0
Everyone is more than welcome to contribute to the above wiki pages,
especially to the upgrade guidelines, to help everyone else during the
migration process from v5.4.x to 5.4.x.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda