Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add AzureServiceClientCredentials
See original GitHub issueThe existing interface ServiceClientCredentials has been working fine for most management plane libraries. However, when it comes to Graph RBAC client, the resourceId field sent in the authorization request is different the other management plane libraries. Thus we would have to use a different credentials for Graph, which requires us to use a different RestClient as well.
To fix this, AzureServiceClientCredentials is introduced to extend ServiceClientCredentials. It
- is still immutable
- requires an
AzureEnvironment - matches the request base URL to the entries in
AzureEnvironmentto figure out where to authenticate and whichresourceIdto send.
This does not only solve the problem for Graph RBAC, but also supports Azure stack scenarios. Developers can create custom AzureEnvironment instances and the implementation of AzureServiceClientCredentials is able to log into public Active Directory service with on-premise resource IDs.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Is there any chance of also adding one other class that extends ServiceClientCredentials type that works with the Storage API (SAS Tokens), which are retrieved from the Insights API?
This would enable the direct retrieval of Azure VM metrics from Azure Storage Tables using only the RestClient from this library (rather than requiring the whole storage SDK).
It’s added and called
AzureTokenCredentials.For now we have no plan to unify the authentication methods across services since there are just too many different needs and requirements.