Skip to content

Add Symphony RSA authentication preset - #105

Merged
timkpaine merged 1 commit into
Point72:mainfrom
timkpaine:feature/symphony-rsa-auth
Oct 6, 2026
Merged

timkpaine merged 1 commit into
Point72:mainfrom
timkpaine:feature/symphony-rsa-auth

Conversation

@timkpaine

Copy link
Copy Markdown
Member

What this adds

backend=symphony_rsa, a Symphony preset that authenticates with an RSA private key.

export SYMPHONY_HOST=... SYMPHONY_BOT_USERNAME=... SYMPHONY_BOT_PRIVATE_KEY_PATH=...
csp-bot-start +gateway=bot '+backend=[symphony_rsa]'

Why

The existing symphony preset authenticates with a certificate, so every bot using an RSA key has to hand-write an override. docs/wiki/Backends.md currently documents exactly that workaround.

RSA is what symphony-bdk configuration files use, and it is what Symphony's Developer Certification sandbox issues — the bundle it hands over contains a config.json pointing at a *-private.pem, with no certificate at all. A preset seems better than asking everyone starting from that bundle to write the override themselves.

The certificate preset is untouched, so nothing changes for existing users. Like it, the RSA preset takes a path rather than key content, keeping long-lived key material out of the process environment.

Verification

Run against a Developer Certification sandbox bot on develop2.symphony.com:

Starting csp_gateway version 3.0.0 / csp_bot version 2.0.2
Created connected backend for symphony
Bot info for symphony: id=349026222366055, name=Dev Cert Bot 9150
Injected 1 connected backends into AgentCommand: ['symphony']

make lint passes. The test suite is 282 passed, 12 failed, and those twelve are ModuleNotFoundError: No module named 'claude_agent_sdk' in my environment — identical on an unmodified checkout, so unrelated to this change.

Docs updated: the credentials table gains the RSA row, the Symphony paragraph describes both presets, and the override example now shows a field neither preset covers rather than the RSA workaround.

The symphony preset authenticates with a certificate, so every bot using
an RSA private key has to hand-write an override. RSA is what symphony-bdk
configurations use and what Symphony's developer sandbox issues, so it is
worth a preset of its own.

backend=symphony_rsa sets bot_private_key_path from
SYMPHONY_BOT_PRIVATE_KEY_PATH, keeping the key on disk rather than in the
environment, as the certificate preset does. The certificate preset is
unchanged.

Verified by running csp-bot against a Symphony developer sandbox bot with
backend=[symphony_rsa]: the config resolves and the bot connects.

Signed-off-by: Tim Paine <[email protected]>
@timkpaine
timkpaine requested a review from ptomecek as a code owner October 6, 2026 23:20
@codecov

codecov Bot commented Oct 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.56%. Comparing base (c641775) to head (5a953b5).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #105   +/-   ##
=======================================
  Coverage   84.56%   84.56%           
=======================================
  Files          44       44           
  Lines        4569     4569           
  Branches      337      337           
=======================================
  Hits         3864     3864           
  Misses        600      600           
  Partials      105      105           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@timkpaine
timkpaine merged commit 18bfd2b into Point72:main Oct 6, 2026
4 checks passed
@timkpaine timkpaine changed the title Add a Symphony backend preset for RSA key authentication Add Symphony RSA authentication preset Oct 8, 2026
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.

1 participant