-
Notifications
You must be signed in to change notification settings - Fork 562
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use Federated credentials with service principal to auth the Azure resources #1362
Comments
If you're using the msodbcsql (17 or 18) driver you can give it the access token directly: https://learn.microsoft.com/en-us/sql/connect/odbc/using-azure-active-directory#authenticating-with-an-access-token |
@gordthompson I wouldn't call this a duplicate without knowing more details about what the OP is trying to accomplish ("federated credentials" is vague and can refer to various things) or indeed if this is the msodbcsql driver being used. |
Thank you so much @v-chojas and @gordthompson! |
Do not specify authentication mode when using access token. |
I got the access token from Does the access token a correct one? I see it returns me Could you provide some insights here? |
You need to add the corresponding account on the server with CREATE USER ... FROM EXTERNAL PROVIDER |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Please first make sure you have looked at:
Environment
To diagnose, we usually need to know the following, including version numbers. On Windows, be
sure to specify 32-bit Python or 64-bit:
Issue
Due to security issue, I cannot use clientid + secret when I use service principal as the authentication method.
Then how can I use federated credentials to do the authentication?
Thank you!
Often it is easiest to describe your issue as "expected behavior" and "observed behavior".
The text was updated successfully, but these errors were encountered: