-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Why client_id value is always the same? #18008
Comments
# this credential will authenticate users to 04b07795-8ddb-461a-bbee-02f9e1bf7b46 (Azure CLI)
DeviceCodeCredential()
# this credential will authenticate users to MY_APPLICATION
DeviceCodeCredential(client_id=MY_APPLICATION) |
All I want to understand here is why if I don't specify my own client_id I will always have client_id with this specific value 04b07795-8ddb-461a-bbee-02f9e1bf7b46 so this value is the default value for Azure AD or what? |
As I wrote above, this is the client ID for the Azure CLI. The login page also points that out: "You're signing in to Microsoft Azure Cross-platform Command Line Interface on another device...". We use it as a default because Azure AD doesn't have a default--a user must authenticate to some specific application. The Azure CLI is a good default for us because we can assume it's registered in a user's tenant and has access to the APIs our clients use. |
Rebase Microsoft.SQL in Main Branch (Azure#18428) * Adds base for updating Microsoft.Sql from version preview/2021-08-01-preview to version 2021-11-01-preview * Updates readme * Updates API version in new specs and examples * update sql default tag to composite-v5 (Azure#17143) * Updated Blob Auditing API Files (Azure#17355) * Updated Blob Auditing API Files * Fixed new property name case * fixing x-ms-enum lint warning Co-authored-by: Mukesh Dogra <[email protected]> * Adding swagger for endpoint certificates (Azure#17156) * Adding swagger for endpoint certificates * Fix the year * Fix build error on the pull request * Microsoft.Sql - adding Database and Server AdvancedThreatProtection APIs (Azure#17881) * Microsoft.Sql - adding Database and Server AdvancedThreatProtection APIs * Fix to Swagger ModelValidation failures * Removing the 201 from Database Upsert operation since it is not a long running operation. * Change the name of the API to AdvancedThreatProtectionSettings * Fix to the renaming to AdvancedThreatProtectionSettings * Remove old files * Adding ManagedServerDnsAliases API endpoints (Azure#18008) * change * Update readme.md * error 201 * Revert "Update readme.md" This reverts commit ceff39a406eefda1ed38c6188fd9d2eb271053ab. * Revert "error 201" This reverts commit 759fa4f92e9967d72060485aa36d7a1b62a9d227. * Fixed bad reverts Co-authored-by: Ji Wang <[email protected]> * Add 201 response example so SQL clients can work correctly (Azure#18121) * Add examples for cross sub restore (Azure#18135) * Release Microsoft.sql 2021 11 01 preview (Azure#18005) * update swagger files and example files * update readme.md * address the pipeline error. * update the reference. * address the pipeline error * address x-ms-secret comments * update error message * revert the deleted legacy files; avoid breaking changes. * remove example files and reference. * remove secret * Adds base for updating Microsoft.Sql from version preview/2021-08-01-preview to version 2021-11-01-preview * Updates readme * Updates API version in new specs and examples * update sql default tag to composite-v5 (Azure#17143) * Updated Blob Auditing API Files (Azure#17355) * Updated Blob Auditing API Files * Fixed new property name case * fixing x-ms-enum lint warning Co-authored-by: Mukesh Dogra <[email protected]> * Adding swagger for endpoint certificates (Azure#17156) * Adding swagger for endpoint certificates * Fix the year * Fix build error on the pull request * Microsoft.Sql - adding Database and Server AdvancedThreatProtection APIs (Azure#17881) * Microsoft.Sql - adding Database and Server AdvancedThreatProtection APIs * Fix to Swagger ModelValidation failures * Removing the 201 from Database Upsert operation since it is not a long running operation. * Change the name of the API to AdvancedThreatProtectionSettings * Fix to the renaming to AdvancedThreatProtectionSettings * Remove old files * update swagger files and example files * update readme.md * address the pipeline error. * resolove the conflict * address the pipeline error * address x-ms-secret comments * update error message * revert the deleted legacy files; avoid breaking changes. * remove example files and reference. * remove secret Co-authored-by: Zhenglai Zhang <[email protected]> Co-authored-by: msdogra <[email protected]> Co-authored-by: Mukesh Dogra <[email protected]> Co-authored-by: srmarkov <[email protected]> Co-authored-by: Uriel Cohen <[email protected]> Co-authored-by: Marko Nikolic <[email protected]> Co-authored-by: Andrija Cicovic <[email protected]> Co-authored-by: Ishan Rajesh Madan <[email protected]>
I am wonder why client_id value if I don't use specific Service Principal is always the same?
client_id=04b07795-8ddb-461a-bbee-02f9e1bf7b46
doesn't matter if I use
az cli
orterraform
.Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: