[destination-SFP-JSON] "configuration check failed" when there is a # in the password

[coffeesandwitch]

Connector Name

SFP-JSON

Connector Version

0.2.15

What step the error happened?

Configuring a new connector

Relevant information

Provide host, user, password and a custom port. clicking 'Set up destination' returns and 'configuration check failed with "An exception occurred: Port could not be cast to integer as '[redacted partial password'.

Relevant log output

error occurs in line 182 of parse.py. I cannot post full stack trace

Contribute

• Yes, I want to contribute

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/12613

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/b251f53a4c5f4a318e12b72968178287

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Matthew White (@coffeesandwitch), thank you for reporting this!

We're looking into this and will escalate it to the team for investigation. The connector name, version, configuration step, and sanitized error message you provided are helpful.

If you're able to share any additional logs, please ensure you mask or remove any sensitive information (API keys, passwords, tokens, connection strings) before posting them.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[devin-ai-integration]

Hi Matthew White (@coffeesandwitch), we've escalated this to our team for investigation: https://github.com/airbytehq/oncall/issues/12613

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.