Special characters not working as mssql password

[maciej-skorupka]

Prerequisites

• I've searched the current open issues
• I've updated to the latest version of Toolbox

Toolbox version

0.7.0

Environment

1. OS type and version: Windows 11
2. How are you running Toolbox:

• As a downloaded binary directly from github

Client

1. Client: running a command line on windows

toolbox.exe --tools-file "tools.yaml" --log-level DEBUG

Expected Behavior

I'd like toolbox to connect to the database even when the password contains special characters

Current Behavior

2025-06-16T17:24:21.8764283+02:00 ERROR "toolbox failed to initialize: unable to initialize source "mysource": unable to connect successfully: parse "sqlserver://username:113%0SoAda2m@somedatabase.database.windows.net:1433?database=mydb": invalid URL escape "%0S""

Steps to reproduce?

1. Run "toolbox.exe --tools-file "tools.yaml" --log-level DEBUG"
2. tools.yaml content:

sources:
    mysource:
        kind: mssql
        host: somedatabase.database.windows.net
        port: 1433
        database: mydb
        user: username
        password: '113%0SoAda2m'
        
        

Additional Details

No response

[maciej-skorupka]

Nevermind. The error made me realize that I can just encode the password inside YAML with URI encoding, so % becomes %25. Nevertheless it might be good to have this mentioned in the docs.

[Yuan325]

@maciej-skorupka Hi, thanks for opening this. Do you meant to set the password field as encoded password?

[maciej-skorupka]

I mean to change % to %25 inside the yaml config. Generally URL encode it.

sources:
    mysource:
        kind: mssql
        host: somedatabase.database.windows.net
        port: 1433
        database: mydb
        user: username
        password: '113%0SoAda2m'

to this:

sources:
    mysource:
        kind: mssql
        host: somedatabase.database.windows.net
        port: 1433
        database: mydb
        user: username
        password: '113%250SoAda2m'

[Yuan325]

@maciej-skorupka Thanks for flagging this. I reopened this issue! This is definitely something we want to fix/address.