Replies: 7 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 |
Beta Was this translation helpful? Give feedback.
-
Hey @v-chojas - Would this be the same issue as documented in the wiki here making this a duplicate of #228 ? |
Beta Was this translation helpful? Give feedback.
-
@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. |
Beta Was this translation helpful? Give feedback.
-
Thank you so much @v-chojas and @gordthompson! |
Beta Was this translation helpful? Give feedback.
-
Do not specify authentication mode when using access token. |
Beta Was this translation helpful? Give feedback.
-
I got the access token from Does the access token a correct one? I see it returns me Could you provide some insights here? |
Beta Was this translation helpful? Give feedback.
-
You need to add the corresponding account on the server with CREATE USER ... FROM EXTERNAL PROVIDER |
Beta Was this translation helpful? Give feedback.
-
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".
Beta Was this translation helpful? Give feedback.
All reactions