Issue Connecting to Azure SQLServer Public Endpoints

[jacobreeves]

Operating System

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:    20.04
Codename:   focal

TinyTDS Version and Information

TinyTds 2.1.1

FreeTDS Version

tsql -C

Compile-time settings (established with the "configure" script)
                            Version: freetds v1.00.91
             freetds.conf directory: /usr/local/etc
     MS db-lib source compatibility: no
        Sybase binary compatibility: no
                      Thread safety: yes
                      iconv library: yes
                        TDS version: 7.3
                              iODBC: no
                           unixodbc: no
              SSPI "trusted" logins: no
                           Kerberos: no
                            OpenSSL: yes
                             GnuTLS: no
                               MARS: no

Description

We are attempting to get TinyTds to connect to an Azure instance via the public endpoint. For public endpoints the host matches the pattern: azure-host.public.some-guid.database.windows.net and the port is 3342.

Using the tsql command below, this works just fine and it connects immediately tsql -H azure-host.public.some-guid.database.windows.net -U username -p 3342 -P password

However, if we attempt to connect using TinyTds from the same host using the command below client=TinyTds::Client.new( :username=> 'username@azure-host', :password=> 'password', :host=>'azure-host.public.some-guid.database.windows.net', :port=>3342, :encoding=>"UTF-8", :azure=>true )

we get the auth error below (pulled from freetds.log) 19:39:55.052288 2790 (token.c:2384):tds_process_info() reading message 18456 from server

So the questions are:

• All of the documentation we've seen around this references SQLServer on the internal SQLServer port of 1433. Does this library work against the public endpoints on 3342?
• The user in the sqlserver db is just 'username'. Why is it required to pass 'username@azure-host'?
• How can we get this to work?

Thanks!

[jacobreeves]

Hi

Just checking to see if anyone has any ideas on this.

Thanks!

[bvogelzang]

Complete guess but have you tried setting the username as username@azure-host.public.some-guid?

[jacobreeves]

Thanks @bvogelzang. Yes. I've tried every permutation I can think of. I've replicated the problem at the FreeTDS level and am going to post a similar issue there.

[aditandrau]

Hello,

Do you have any updates on this issue?

We are encountering the same issue.

Thanks!

[jacobreeves]

Hi @aditandrau. Unfortunately, the only update we have is an issue opened against the underlying FreeTDS library here.