You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we can use credential manager to configure and manage connections (formerly called authorizations) for backend OAuth 2.0 APIs.
It could be great to have this support in apiops
There might be some challenges on handling secrets(client secrets) to be passed as till now there is no native support for keyvault to fetch the secret directly into credentials manager. But as a suggestion we can look into environment variables instead of putting into yaml/source control
The text was updated successfully, but these errors were encountered:
Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
Please describe the feature.
Currently, we can use credential manager to configure and manage connections (formerly called authorizations) for backend OAuth 2.0 APIs.
It could be great to have this support in apiops
There might be some challenges on handling secrets(client secrets) to be passed as till now there is no native support for keyvault to fetch the secret directly into credentials manager. But as a suggestion we can look into environment variables instead of putting into yaml/source control
The text was updated successfully, but these errors were encountered: