How To: reloading TLS certificates on v0.16

[rtk0c]

Topic

TLDR: you need an API token with at least these permissions: authenticate "Sign in to the server", sysActionCreate "Actions Management: Create actions", actionReloadTlsCertificates "Action: Reload: TLS certificates". Then:

stalwart-cli --url=$YOUR_SERVER_HOST --api-key=$YOUR_API_KEY create Action/ReloadTlsCertificates

# OR if you don't want to download the cli:

curl -X POST 'https://$YOUR_SERVER_HOST/jmap' \
  -H "Authorization: Bearer $YOUR_API_TOKEN" \
  -H 'Content-Type: application/json' \
  --data-raw '{"using":["urn:ietf:params:jmap:core","urn:stalwart:jmap"],"methodCalls":[["x:Action/set",{"accountId":"b","create":{"action-0":{"@type":"ReloadTlsCertificates"}}},"0"]]}'

The documentation for certificates manages to be incredibly terse (and unhelpful). Digging through the JMAP schema one can quickly finds the relevant entry https://stalw.art/docs/ref/object/action/#type-reloadtlscertificates but it doesn't tell you how to use it.

The schema reference say you should POST to /api but that doesn't work. Looking at the web UI through dev tools, it seems like it posts to /jmap instead and that works.

Acknowledgement

• I have reviewed the documentation and the FAQ and confirm that my question is not addressed there.
• I understand that maintainers no longer answer support questions through GitHub Discussions, and that for an official response from the Stalwart team I need to post my question at support.stalw.art.
• I agree to follow the project's Code of Conduct.

[github-actions[bot]]

Hi @rtk0c, thanks for posting!

Stalwart support has moved to support.stalw.art. The support portal is now the canonical place to ask questions, request help, and report issues for triage. Other community members may still reply here, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it on the portal.

You can sign in to support.stalw.art with your existing GitHub account, so no separate registration is required. Google, Discord, LinkedIn, and email/password sign-in are also available.

Why we are unifying our support channels

Until now, Stalwart support has been spread across GitHub Discussions, Discord, Matrix, and Reddit. As the project has grown, tracking parallel inboxes and deduplicating threads has become unsustainable; the result has been slower answers, repeated work for the people helping out, and good information buried in chat scrollback where the next person with the same question would never find it.

support.stalw.art is a Discourse instance that we operate ourselves, hosted at Hetzner in Germany and GDPR-compliant.

Thank you for helping us keep the conversation in one place.

[rtk0c]

hm turns out there is already a post #3119
it's just github's discussion search is terrible and I didn't find it the first time. I only found it afterwards by going through the forums again https://support.stalw.art/t/certificate-reload-through-jmap-api/19