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

ConnectWithManagedIdentity is not working after upgrading to 3.0 #9229

Closed
3 tasks
klogan12 opened this issue Dec 20, 2019 · 3 comments
Closed
3 tasks

ConnectWithManagedIdentity is not working after upgrading to 3.0 #9229

klogan12 opened this issue Dec 20, 2019 · 3 comments
Labels
App Configuration Azure.ApplicationModel.Configuration Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@klogan12
Copy link

Describe the bug
ConnectWithManagedIdentity is not working after upgrading to 3.0

Exception or Stack Trace
Add the exception log and stack trace if available

To Reproduce
Follow below doc , but looks like ConnectWithManagedIdentity got removed.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/howto-integrate-azure-managed-service-identity

Code Snippet
Add the code snippet that causes the issue.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

  • OS: [e.g. iOS]
  • IDE : [e.g. IntelliJ]
  • Version of the Library used

Additional context
Add any other context about the problem here.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Bug Description Added
  • Repro Steps Added
  • Setup information Added
@triage-new-issues triage-new-issues bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 20, 2019
@tg-msft tg-msft added App Configuration Azure.ApplicationModel.Configuration Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention Workflow: This issue is responsible by Azure service team. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Dec 23, 2019
@wantedfast
Copy link
Contributor

According the release notes, ConnectWithManagedIdentity() method was removed in 3.0.0 to connect the App Configuration store using system-assigned managed identity currently. And it replaced as Connect() method.

Before:
IConfigurationBuilder configBuilder = new ConfigurationBuilder(); IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => { options.ConnectWithManagedIdentity(endpoint); }).Build();

After
IConfigurationBuilder configBuilder = new ConfigurationBuilder(); IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => { options.Connect(endpoint, new ManagedIdentityCredential()); }).Build();

@wantedfast
Copy link
Contributor

@jongio

@klogan12
Copy link
Author

worked!

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Apr 29, 2020
Merge pull request #1 from Azure/dev-storagesync-Microsoft.StorageSync-2020-03-01

StorageSync - Add enum to few properties (Azure#9229)
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
App Configuration Azure.ApplicationModel.Configuration Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants