Skip to content
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

[Identity] [Docs] Document that ManagedIdentityCredential supports client IDs when working with AKS pods #22154

Closed
sadasant opened this issue Jun 8, 2021 · 1 comment
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. Docs

Comments

@sadasant
Copy link

sadasant commented Jun 8, 2021

Recently, a customer of the NodeJS Identity SDK had some doubts on whether they would be able to use the ManagedIdentityCredential to authenticate using an App Registration client ID. Turns out, it is in fact possible to authenticate with an App Registration client ID using the ManagedIdentityCredential, but only in AKS pods. To help clarify this, I’ve started updating the documentation to reflect that this is possible: Azure/azure-sdk-for-js#15518

Since this should be possible across languages, I’m making this issue to help track the documentation update.

@g2vinay
Copy link
Member

g2vinay commented Oct 29, 2021

Resolved

@g2vinay g2vinay closed this as completed Oct 29, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this issue Feb 2, 2023
Dev keyvault microsoft.key vault 2022 02 01 preview swagger completeness (Azure#22154)

* Adds base for updating Microsoft.KeyVault from version stable/2022-07-01 to version 2022-02-01-preview

* Updates readme

* Updates API version in new specs and examples

* Fixed breaking changes in managedHsm.json. (Azure#22112)

Fixed LRO_RESPONSE_HEADER, INVALID_REQUEST_PARAMETER and OBJECT_MISSING_REQUIRED_PROPERTY errors.

Co-authored-by: Rahul Alapati <[email protected]>

* Undid the API version changes to the Vaults_List API (Azure#22142)

* Fixed breaking changes in managedHsm.json.
Fixed LRO_RESPONSE_HEADER, INVALID_REQUEST_PARAMETER and OBJECT_MISSING_REQUIRED_PROPERTY errors.

* Undid the API Version change to the VaultListFilterTypes API.

Co-authored-by: Rahul Alapati <[email protected]>

* Update listVault.json (Azure#22155)

* Update listVault.json

* Remove the preview API version for the enum

* Delete Vault_Lists API specification

* Added the Vaults_List swagger specification back.

* Abstracted Vaults_List API into 2015-11-01 directory to Swagger ModelValidation Errors.

* Resolved unresolvable references.

* Reorganized the definitions.

* Reorganized the 2015-11-01 directory under 2022-02-01-preview

* Moved the 2015-11-10 directory to stable.

* Undo the abstraction changes.

* Readd the listVault.json.

* Added suppression directives for INVALID_REQUEST_PARAMETER and OBJECT_MISSING_REQUIRED_PROPERTY.

* Modify suppress rule.

* Update the suppression directive.

* Update suppression directive.

* Update suppression directive.

* Update suppression directives.

* Updated suppression directive.

* Added suppression directives for INVALID_REQUEST_PARAMETER, OBJECT_MISSING_REQUIRED_PROPERTY

* Updated suppression directives.

* Updated suppression directives.

* Updated suppression directives.

* Updated suppression directives.

* Updated suppression directives.

* Added x-ms-validation rules to the api-version parameter.

* Updated suppression directives.

* Added individual suppression directives.

* Removed where clause from the OBJECT_MISSING_REQUIRED_PROPERTY suppression directive.

* Corrected yaml title for suppression directives.

Co-authored-by: Rahul Alapati <[email protected]>

---------

Co-authored-by: Rahul Alapati <[email protected]>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. Docs
Projects
None yet
Development

No branches or pull requests

2 participants