Encrypted inter-component communication for Web Modeler

[engineering-issue-sync-app[bot]]

Request via SUPPORT-22238

What should we do?

Support encrypted communication

• from webapp to restapi
• from restapi to websockets
• from frontend to websockets ✅ already supported

Why should we do it?

Customer request, see https://jira.camunda.com/browse/SUPPORT-22238

Acceptance Criteria (MoSCoW prioritized)

• [x] (M) support encrypted communication from webapp to restapi
• [x] (M) support encrypted communication from restapi to websockets
• [x] (M) TLS certificate can be configured for restapi (✅ already supported)
• [x] (M) TLS certificate can be configured for webapp
• [x] (M) TLS certificate can be configured for websockets (https://github.com/camunda/camunda-laravel-websockets/issues/408)
• [x] (M) Documentation

#

Definition of Ready - Checklist

• [x] the issue has a meaningful title, description and testable acceptance criteria
• [x] edge cases and limitations are clear
• [x] unclear requirements have been broken down into separate issues (always make progress)

^{:robot: This issue is automatically synced from: source}

[HanselIdes]

@wollefitz do you think we can close out this ticket?

[wollefitz]

@wollefitz do you think we can close out this ticket?

~It will be automatically closed once https://github.com/camunda/camunda-docs/pull/3933 is merged but feel free to close it already to make transparent that this was released.~

Closed now that https://github.com/camunda/camunda-docs/pull/3933 was merged.