ODBC in Excel with SSO/external authentication (OSX) - snowflake-cloud-data-platform

I have successfully set up and tested an ODBC connection on OSX to a Snowflake instance, using external SSO authentication. Testing was done using iODBC.
However, when I attempt to use the driver in MS Excel for OSX, at the authentication via external web browser stage, I am getting an 'Operation Not Permitted' error. Is it possible to use ODBC with external browser authentication within Excel?

I've seen this error with Excel on Mac as well. Last I heard, Microsoft Support determined that this functionality is not, and will not be supported in Excel for Mac. Feel free to open a ticket with Microsoft if you'd like to see this supported.

Related

How to Access Azure SQL Server/Database from Tableau Desktop using Active Directory Authentication

Can someone let me know why I'm unable to access our Azure SQL Database using Tableau Desktop with our Active Directory account?
I have no problem gaining access using Username and Password, but can't access using AD account i.e. usernam#company.com
I'm getting the following errors
Check whether you have installed ODBC Driver or not. If that's the case, try installing it by following this Download link depending on the operating system you are using.
After installing it, configure the ODBC DSN that may help you to resolve the error.
If it's already installed and still you are getting error, try degrading/upgrading the version.
Take a look at this similar problem answered in below reference:
Error connecting to MySQL - Error Code: B19090E0
You need to configure the server to access using AD account https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-powershell

I cannot authenticate user in SSMS for linked server (snowflake)

Similar problem to one reported here:
Can't create linked server to Snowflake
Difference is while connecting to snowflake I cannot authenticate user in the SSMS:
ODBC driver must be verified by external browser (no password) but it is not happening here. Internet browser in SSMS is working fine, but it is not used to authenticate ODBC user. Configuration of ODBC is fine, as it is working in PowerBI and starting authentication process in default internet browser. Any ideas?
ODBC driver must be verified by external browser
Linked server connections run in the SQL Server process, so there's no interactive access to the desktop to do any kind of interactive authentication.

Connect MuleSoft to SQL Server with an AD User

I am trying to get MuleSoft to talk to a SQL Server using an Active Directory User.
I have gotten it to connect using a user defined in SQL Server, however our DBAs are saying we have to connect with an AD User.
I am getting "login failed" errors
java.sql.SQLException: Cannot get connection for URL jdbc:sqlserver://AG-Q4Test1:1433;databaseName=T10SRV01 : Login failed for user 'HQ\MuleSoftSvc'
I have tried to connect using my credentials and have received the same error. I can connect using SQL Management Studio with my credentials.
I am using the Microsoft SQL Server Driver com.microsoft.sqlserver:mssql-jdbc.6.2.2.jre8
I am thinking that is because its using Windows Authentication
But will this work in CloudHub?
The method described in the KB article will not work in CloudHub because applications don't run in Windows. Take into account that you should not make any assumptions on the operating system and platform for applications deployed on CloudHub.
I was able get Windows Auth working from my local runtime using this article.
After more digging I found this KB Article from MuleSoft which states that Windows Auth is not supported in CloudHub.

Connecting to SharePoint from SSIS using OData Source

I am trying to connect to SharePoint hosted on the Microsoft cloud using the OData source. I am trying to pull the Project related data into the sql table from the SharePoint list and process it into the data warehouse.
When I manually login into the SharePoint ,it has got the necessary permissions to read the data and export into excel. But when I connect through the Odata Source in 2012, I encounter the below error. I am using the visual studio Professional 2015 for the SSIS development.
Identity Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in.
(Microsoft.SqlServer.IntegrationServices.ODataConnectionManager)
Has any one of you encountered this issue any time?
I was able to download the list data from sharepoint to SQL using the 32 bit OData source component.The trick is to use the suffix "/_vti_bin/listdata.svc".
For Ex: If your URL for the List data is :https://sharepoint.com/sales the service document location URL should look like
https://sharepoint.com/Sales/_vti_bin/listdata.svc. Also Enable the Microsoft Online Services Authentication=True in the Connection manager settings.
Thank you
Sharath

MS-Access SSPI error with .adp

I have an old Access project (.adp) that was tied to a SQL Server database using integrated authentication. The .adp is only used this time of year. Since its last use, the SQL Server has been virtualized and patched to current. When I try to open the .adp, it gives me a "Cannot generate SSPI context" error. I got this with another .mdb and just remapped the linked tables through ODBC with a SQL Server login (integrated authentication is not a requirement). However, with this .adp file, just about all the options are greyed out. For example, Linked Table Manager and ODBC Database buttons are greyed out. I can't see any tables, nor apparently link or import any. Is there a way to remove integrated authentication from an .adp project? Or can I convert the database to an .mdb (exporting objects appears greyed out as well)?
NOTE: This is a limited use database with few users on its way out, so I'm very open to "creative" workarounds that don't require me rebuilding the whole thing.
Please, review the following:
Check that SQL Server allow integrated authentication
Your machine (where you open the adp project) and the server are both in the same
domain.
That error is typical when the client machine belongs to another domain or not belongs to any domain.

Resources