<div>Dear all,<br></div><div><br></div><div>I am trying to set up session storage with a SQL Server for our shibboleth SP3 but can not get shibboleth to connect to SQL Server DB.<br></div><div><br></div><div>In our shibboleth2.xml we have the following connection string:<br></div><div><br></div><div>"<ConnectionString>DRIVER=freetds;SERVER=mssql.shared-shibboleth_default;UID=<user>;PWD=<pwd>;DATABASE=shibboleth;APP=shibboleth</ConnectionString>"<br></div><div><br></div><div>Unfortunately, with this configuration I get:<br></div><div><br></div><div>"ODBC Error: 08S01:2:20009:[FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist"<br></div><div><br></div><div class="protonmail_signature_block protonmail_signature_block-empty"><div class="protonmail_signature_block-user protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty">When I try to connect to the db from the command line within the shibboleth container like so "tsql -S mssql -U sa -P Testing0! -D shibboleth" i get a working connection. </div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty">Note: For the tsql command both mssql and mssql.shared-shibboleth_default work as server. (Both versions have been unsuccessfully tried for the connection string as well)</div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div>We're using shibboleth 3.1.0 running on centOS8 and SQL Server 2019, SQL Server is running on default port 1433, both SP3 & MSSql are dockerized and share the "shared-shibboleth_default" network.<br></div><div><br></div><div>Any kind of help or pointers as to what to try or better debug this issue are much appreciated.<br></div><div><br></div><div>Best,<br></div><div>Thomas Rudolf<br></div><div><br></div><div><br></div>