Hello OpenZaak community,
As you might have seen, the Foundation for Public Code will be winding down
the office in Europe (see this blog post:
https://blog.publiccode.net/news/2024/02/28/changes-at-the-europe-office.ht…
)
Therefore, we will no longer be able to steward the OpenZaak codebase to
the level which we aspire and want to be frank with you about stepping back.
Expect incoming pull requests that will be removing the references to
stewardship by the Foundation for Public Code from the repositories soon.
We are pleased to say that we perceive the collaboration in the technical
steering calls to be both productive and self-sufficient.
Best regards,
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop
Foundation for Public Code https://publiccode.net
Beste,
Met veel interesse volg ik de ontwikkelingen. Graag ontvang ik een uitnodiging tot de Maandelijkse Technical Steering call.
Met vriendelijke groet,
Adil Saber
Functioneel Beheer eSuite
Gemeente Rotterdam
Bestuurs- en concernondersteuning
Afdeling FB Generiek
De Rotterdam, Wilhelminakade 179
Postbus 1130 3000 BC Rotterdam
Mobiel 0638319515
Website www.rotterdam.nl<http://www.rotterdam.nl/>
All,
Currently, JWTs in Open Zaak are a) valid for 1 hour and b) have no leeway.
This means:
a) Clients can generate a JWT, and use this token for 1 hour. After 1 hour,
the token will no longer work and the client needs to generate a new one.
b) Because there is no leeway, if there is some time difference between the
client and the server. A token that is valid on the client until 12:00:00
and the client is 5 behind the time the server, the token will no longer be
valid at 11:59:55.
The question arose to increase the JWT default duration from 1 hour to 1
day and to increase the default leeway to 5 seconds.
Input and thoughts are appreciated.
Best regards,
Joeri Bekker
--
Maykin
Keizersgracht 117, 1015 CJ Amsterdam
tel.: +31 (0)20 753 05 23
http://www.maykinmedia.nl
Hi folks,
Today we released Open Zaak 1.8.0. The big features/improvements are:
- Upgraded to Zaken API 1.2.0
- Upgraded to Documenten API 1.1.0
- Added assured delivery for notification publishing
- Improved support for managing external API references (e.g. using an
external Documents API with Open Zaak)
- Performance improvements.
This brings us almost up to par with the latest and greatest API standards
published by VNG, containing some highly-requested features. We have also
worked on reliability and performance of the zaak-create endpoint, with
benchmarks showing more than 140,000 cases created per hour by concurrent
clients with a 0% error rate!
This release also (as usual) contains a number of bugfixes and project
maintenance related improvements. The full changelog is available on
readthedocs
<https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1>.
*Note that upgrading to this release requires some infrastructure changes,
so please carefully review the release notes.*
The container image is available on Docker Hub and bug reports can be filed
on Github.
Best,
Sergei
Hi All,
There are some points to be discusses and an invite has been send for the 7th September at 14 pm.
If you're not invited and part of the Technical team, let me know via mail or slack.
Hackmd file with coming notes, agenda points can be added here ==>
https://hackmd.io/d8j8ub9_SxqSEDoxDfD2Gw
Met vriendelijke groet,
[cid:image001.png@01D8B24B.052F8000]
Tahir Shazad Malik
email
tahir.malik(a)contezza.nl<mailto:tahir.malik@contezza.nl>
mobile
+31 (0)6 14 77 50 82
office
+31 (0)848 68 89 02
website
www.contezza.nl<http://www.contezza.nl/>
[linkedIn]<https://www.linkedin.com/in/tsmalik/>
[Twitter]<http://twitter.com/tahirshazad/>
Afwezig: vrijdag
Hi folks,
Open Zaak 1.7.0 was just released and Open Notificaties 1.4 was released a
couple weeks ago.
The new version of Open Zaak implements Zaken API 1.1 and Catalogi API 1.1
- a step towards implementing all the latest versions of the API's from the
standard. We've also made a number of improvements to the Catalogi Admin
environment which will be welcomed by your admins designing "zaaktypen" :-)
Finally, we managed to also fix a number of bugs in Open Zaak again. The
full changelog is available on the documentation website
<https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1%3E>
.
Open Notificaties 1.4 implements some controls to ensure delivery of
notifications to subscribers, meaning it will keep retrying a number of
times before giving up. The full details and how you can configure this are
also specified in the documentation
<https://open-notificaties.readthedocs.io/en/stable/changelog.html#id1%3E.>.
Once the build has completed, all images will be available on Docker Hub
again. Issues and bugs can still be reported to Github.
Best,
Sergei
Hi everyone - this is a notice for the sake of transparency with regard to
a potential security vulnerability.
The Django team released security fixes related to potential SQL
injections. We've audited the Open Zaak code and found no vulnerable code
paths that make this exploitable.
Updating to new patch versions is tracked on Github:
https://github.com/open-zaak/open-zaak/issues/1207
Hi everyone - this is a notice for the sake of transparency with regard to
a potential security vulnerability.
The Django team released security fixes related to potential SQL
injections. We've audited the Open Zaak code and found no vulnerable code
paths that make this exploitable.
To track this and prevent it in the future, I've created a Github issue:
https://github.com/open-zaak/open-zaak/issues/1136
Hello,
We're delighted to see that OpenZaak now meet 12 out of 15 criteria of the
Standard for Public Code:
https://github.com/open-zaak/open-zaak/blob/main/docs/introduction/open-sou…
Of the remaining criteria, some may already be covered and only need
re-review and discussion, whereas others, like "Use plain English" would
require investing in improving the codebase and documentation.
We would like to hear what ambitions the community has this year to get
movement on meeting the Standard for Public Code.
Best regards,
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net