Skip to main content
A
abhishekd257618
September 24, 2025
Question

SQL Server Connected system OAuth2.0 Test failure

  • September 24, 2025
  • 8 replies
  • 0 views

Hi, 

While trying to connect to SQL Server connected system using OAuth 2.0, the test connection is failing. 
i am trying to connect via service principal. The token generation is successful (tested separately) but in the connected system for SQL Server, it is not working at all. 
Please advise,

Refer Attached screenshots

8 replies

shubhama926776
shubhama926776
September 24, 2025

My guess, The issue is the SQL Server database user for the service principal (Client Id)is not created or lacks permissions.

Try below links for reference
https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-service-principal?view=azuresql
https://learn.microsoft.com/en-us/sql/connect/jdbc/connecting-using-azure-active-directory-authentication?view=sql-server-ver17
https://docs.appian.com/suite/help/25.3/setting_up_an_oauth_connected_system.html
https://docs.appian.com/suite/help/25.3/Configuring_Relational_Databases.html#sql-server

A
abhishekd257618Author
September 29, 2025

Hi,
There was an IP whitelist issue on the firewall and we got it fixed to ensure the VPN tunnel connectivity. 
however, a new error is being faced saying invalid credentials. Internally, we are able to use the same service principal successfully. not sure what could be done next. 
The logs shows the below error: 

2025-09-29 18:44:13,781 [ConnectionTimeoutBasicDataSource-0] INFO  com.appiancorp.connectedsystems.http.oauth.HttpOAuthTokenRetriever - Error while retrieving token: unauthorized attempting to pass Authentication in body
2025-09-29 18:44:13,950 [ConnectionTimeoutBasicDataSource-0] INFO  com.appiancorp.connectedsystems.http.oauth.HttpOAuthTokenRetriever - Error while retrieving token using auth in body: unauthorized


shubhama926776
shubhama926776
September 30, 2025

Client Id, client secret, or token endpoint is incorrect or the OAuth credentials are not sent as parameters in the request body exactly as expected.

J
jessek855119
September 24, 2025

There should be a more concise error in System Logs > tomcat-stdOut.log. Could you post that exception here? Without a more concise error, we're guessing about many variables related to your Appian configuration and where your database lives.

IF your database is in Azure Cloud, also check these:

  • On a different project / platform, AzureTenant JDBC property needed to be added to the JDBC connection string for a Teams integration that also used ServicePrincipal. I'm not sure if that applies to your situation, but it's pretty easy to test.
  • Appian might have additional VPN requirements depending on your environment's configuration:
    docs.appian.com/.../Microsoft_Azure_DB_Integration_Appian_Cloud.html
davidj137213
davidj137213
September 25, 2025

Check logs please and share the error...

Terms & ConditionsAccessibility statement