Windows authentication (Non Shared) is not prompting for credentials any more

[WheresWally]

Hi All, 

Our app was working well for users until this Monday 10th of June when they all then reported receiving a credentials invalid or missing error when the app tried connecting to the on prem sql database (via our gateway). 

I checked the our environment had the per app licences assigned and I tried removing all of the connections and testing them one by one. None would work. I checked that our gateway had the users as connection creators for SQL still which it does. 

I created an entirely new app with only one clearcollect button on a SQL table via a brand NEW connection using Windows (Non Shared) for authentication. Same error for my user. 

I switched out that connection for a normal windows authentication (so shared), and the connection worked immediately for the user. 

Note that for both types of connections, when first opening this brand new app, the user was prompted with the attached prompt including an allow button. Notable, for the NON shared version, it did not prompt for credentials - this is the issue I believe. It always used to prompt for them on the first time using an app/connection. Now it doesn't. And if you already stored them before this issue started, it doesn't seem to remember them. 

Can somebody else please try using windows non shared to an on prem sql server via gateway and let me know if they're prompted for credentials that stay and work?

Thanks

[WheresWally]

I should add that this is important to us because non-shared means that our data is secured at the database level for what the user has access to. As opposed to them just using my stored credentials which have access to more. 

[WheresWally]

tagging @Pstork1 as I think you're the expert in the area. Thanks

[Pstork1]

I would double check that you are actually set for Windows AD Authentication and not Windows EntraID Authentication. That is the change that I think was recently enacted.  It used to be Windows Auth (AD) or Azure AD in the cloud. Now you can use EntraID on premises also.  SQL Server - Connectors | Microsoft Learn

[WheresWally]

Hi @Pstork1 , Thanks so much for the lead. Do you know how recent the change was? We've had windows non-shared working for a while now and I'm not sure why for an entirely new user and app and connection it would no longer prompt for credentials but only ask to allow and then fail in app. 

The only other option I saw and have just tested was 'Microsoft Entra ID Integrated' which I tested and got the error below. Note I didn't see anything about our gateway during the connect process with this method. Also, creating the windows non shared still works (accepts my credentials, loads the tables and works in app), it just doesn't work for an end user loading the app who is no longer prompted for SQL credentials when starting the app for the first time. 

Error I saw:

"The tables didn't load correctly...

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

[Pstork1]

Sorry, I don't know how recent the change was. I suspect there were a number of changes that rolled out in connection with Build, but I don't know that this is one of them.