AAD Universal with MFA - error
Azhkanizkael
Posts: 25 Bronze 2
I followed the guide for setup for using AAD Universal with MFA to connect to a database, but once successfully authenticated in the browser, I'm met with the following error:
Unable to obtain connection from database (jdbc:sqlserver://xxx.yyy.database.windows.net;authentication=activeDirectoryInteractive;databaseName=zzz;encrypt=true;integratedSecurity=false) for user '': Cannot set the AccessToken property if "Authentication" has been specified in the connection string. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- SQL State : null Error Code : 0 Message : Cannot set the AccessToken property if "Authentication" has been specified in the connection string.
Is there something I missed in the setup or something not connected correctly?
Unable to obtain connection from database (jdbc:sqlserver://xxx.yyy.database.windows.net;authentication=activeDirectoryInteractive;databaseName=zzz;encrypt=true;integratedSecurity=false) for user '': Cannot set the AccessToken property if "Authentication" has been specified in the connection string. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- SQL State : null Error Code : 0 Message : Cannot set the AccessToken property if "Authentication" has been specified in the connection string.
Is there something I missed in the setup or something not connected correctly?
Tagged:
Answers
Flyway Engine: 9.10.2
Git: 2.22.0
Redgate Compare: 1.6.0.7305
The application itself didn't know there was an update, so I had to manually update.
Indeed this issue was resolved in 6.0.1 so later version should have this fixed.