Skip to content

fix: [stable-9.0][OCISDEV-1687] pass enabletls to the jsoncs3 share manager and OCM - #13444

Open
2403905 wants to merge 3 commits into
stable-9.0from
fix/OCISDEV-1687-jsoncs3-nats-tls-stable-9.0
Open

2403905 wants to merge 3 commits into
stable-9.0from
fix/OCISDEV-1687-jsoncs3-nats-tls-stable-9.0

Conversation

@2403905

@2403905 2403905 commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

The sharing service did not give OCIS_EVENTS_ENABLE_TLS to the jsoncs3 share manager. The ocm service did not give it to the sciencemesh and the ocmcore event connections. reva reads the enabletls key in all three places. Without the key, reva did not add the TLS options. Thus the client did not use OCIS_EVENTS_TLS_ROOT_CA_CERTIFICATE.

With a NATS server that uses TLS with a private CA, these connections failed with x509: certificate signed by unknown authority. The services tried again for up to 15 minutes. The health check uses the full config, so the pods stayed Ready.

  • Add enabletls to the jsoncs3 events map in services/sharing/pkg/revaconfig/config.go.
  • Add enabletls to the sciencemesh and the ocmcore events maps in services/ocm/pkg/revaconfig/config.go.
  • Add unit tests that check all the NATS keys of each events map in the sharing and the ocm services.

The fix is in oCIS only. reva needs no change.

This is the backport of #13443 to stable-9.0. The backport to stable-8.0 is #13442.

🤖 Generated with Claude Code

@2403905
2403905 requested a review from a team as a code owner November 12, 2026 12:19
@kw-security

kw-security commented Nov 12, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

2403905 and others added 2 commits November 12, 2026 14:02
The events map of the jsoncs3 share manager did not have the enabletls
key. Thus reva did not add the TLS options. The client did not use the
root CA certificate. The connection to a NATS server with a private CA
failed with "x509: certificate signed by unknown authority".

The map now gets cfg.Events.EnableTLS. A new unit test checks all the
NATS keys of the jsoncs3 events map and of the events middleware.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Roman Perekhod <2403905@gmail.com>
(cherry picked from commit 4469b6d)
…e events

The sciencemesh and the ocmcore events maps did not have the enabletls
key. reva reads this key in both services. Thus these connections did
not use TLS options and did not use the root CA certificate.

Both maps now get cfg.Events.EnableTLS. A new unit test checks all the
NATS keys of both events maps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Roman Perekhod <2403905@gmail.com>
(cherry picked from commit 3b3eb5f)
@2403905
2403905 force-pushed the fix/OCISDEV-1687-jsoncs3-nats-tls-stable-9.0 branch from b93c22f to 22c7745 Compare November 12, 2026 13:03
@2403905 2403905 changed the title fix: [stable-9.0][OCISDEV-1687] pass enabletls to the jsoncs3 share manager fix: [stable-9.0][OCISDEV-1687] pass enabletls to the jsoncs3 share manager and OCM Nov 12, 2026
@2403905
2403905 enabled auto-merge (squash) November 13, 2026 18:30

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants