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.

Sign up for GitHub

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

Jump to bottom

Use SharedTokenCacheCredential in Container #13404

Closed
cxznmhdcxz opened this issue Aug 28, 2020 · 1 comment
Closed

Use SharedTokenCacheCredential in Container #13404

cxznmhdcxz opened this issue Aug 28, 2020 · 1 comment
Labels
needs-triage This is a new issue that needs to be triaged to the appropriate team.

Comments

@cxznmhdcxz
Copy link
Member

pacakge: azure-identity==1.4.0
Identity E2E test in containers
Live test every credential of azure-identity in container.

Is it possible to use SharedTokenCacheCredential in container?
Tried mapping volumes but no good, there's decode error. Most likely because container is Linux image and local is Windows system?
Need a good way to use SharedTokenCacheCredential in a container, thank you.

@jongio
@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Aug 28, 2020
@chlowell
Copy link
Contributor

The scenario you tried, mounting a Windows host's cache into a container, won't work (even in a Windows container) because only the local user on the host can decrypt the cache. It is however possible when the cache is plaintext or was created in the container. But we wouldn't suggest people try to use this credential in container scenarios--really it isn't appropriate for them--so it's not important to test.

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this issue Mar 29, 2021
@xaliciayang @ayeletshpigelman
@strehan1993 @kukislav @athreya-geetha
CodeGen from PR 13689 in Azure/azure-rest-api-specs
9a69d40 
Dev sql microsoft.sql 2020 11 01 preview minor change (Azure#13689)

* Adds base for updating Microsoft.Sql from version preview/2020-08-01-preview to version 2020-11-01-preview

* Updates readme

* Updates API version in new specs and examples

* Add updated 2020-11-01-preview versions of LongTermRetenionBackups.json and Databases.json (Azure#12146)

* add updated databases.json swagger

* update readme with new package

* v4 -> v5

* add missing chunk in readme

* add correct swaggeR

* add examples

* add correct examplese

* remove unreferenced examples

* update swagger and examples. add 2020-11 pure package

* Fix reference to 2020-08-01 reference to ElasticPools.json

* update Databases.json name

* update examples

* remove nonexistant swagger

* fixed reference capitals in readme

* update package composite and fix ref to ManagedInstances.jsON

* make backupstorageredundancy settings consistent

* add requestedBackupStorageRedundancy to properties object in example

* add LTR swagger and examples

* add LTR Policies swagger and examples

* make v5 match v4

* add updated Databses.json

* merge conflicts in LTR Policies swagger'

* take out comments in readme

* taking ImportExport.json out from 2020-11 package

* remove duplicate 2020-11 tag in readme

* modify Databases_legacy.json to exclude ImportExport-related APIs

* add servers.json for IE APIS and remove unused databases examples

* fix model & prettier errors; add missing server example

* add missing servers examples

* fix example to exclude property from server obj

* change RecommendedActions definitoins

* change tag to composite v4

* Add missing properties for api version 2020-02-02-preview of securityAlertPolicies (Azure#13117)

* Add missing properties for api version 2020-02-02-preview

* fix checks

* fix according to prettier check

* Add the change to version 2020-08-01-preview and version 2020-11-01-preview

* remove changes in package-lock

* Add new line at the end of file

* update version 2020-11-01-preview

* Update the ref to system data in serverdevopsaudit

* add missing point

* fix the validation errors

* Delete ServerDevOpsAudit.json

* fix the validation errors

* re add ServerDevOpsAudit.json

* fix the validation errors (Azure#13325)

* fix the validation errors

* Delete ServerDevOpsAudit.json

* fix the validation errors

* re add ServerDevOpsAudit.json

* address PrivateEndpointConnections.json validation issues in v3, v2 and v1

* Address Private Endpoint validation issues in V3, V2 and V1 SDK tags (Azure#13404)

* fix the validation errors

* Delete ServerDevOpsAudit.json

* fix the validation errors

* re add ServerDevOpsAudit.json

* address PrivateEndpointConnections.json validation issues in v3, v2 and v1

* Identity/Key/external Admin API (Azure#13411)

* Add examples for sql mi remove maintenance configuration (Azure#13390)

* Add missing specs 2020 11 01 (Azure#13488)

* fix the validation errors

* Delete ServerDevOpsAudit.json

* fix the validation errors

* re add ServerDevOpsAudit.json

* address PrivateEndpointConnections.json validation issues in v3, v2 and v1

* add missing specs in 2020-11-01-preview

* update the validation errors

* update systemData and sync with global common/v1/types.json

* update legacy to match the latest database specs

* remove RestorableDroppedManagedInstances due to it should be internal

* Updated database extensions (Azure#13584)

Co-authored-by: Geetha Athreya <geathrey@microsoft.com>

Co-authored-by: xaliciayang <59986952+xaliciayang@users.noreply.github.com>
Co-authored-by: ayeletshpigelman <ayshpige@microsoft.com>
Co-authored-by: strehan1993 <70013163+strehan1993@users.noreply.github.com>
Co-authored-by: Ivan Kulezic <72797230+kukislav@users.noreply.github.com>
Co-authored-by: Geetha Athreya <43223869+athreya-geetha@users.noreply.github.com>
Co-authored-by: Geetha Athreya <geathrey@microsoft.com>
@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.
Assignees
No one assigned
Labels
needs-triage This is a new issue that needs to be triaged to the appropriate team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chlowell @cxznmhdcxz