[FEATURE REQ] Support for Credentials and Credentials Manager

Open
#733 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, csharp
Domain
api, cloud

Research direction

Start with the Azure API Management credentials overview linked in the issue, then inspect APIOps configuration and deployment paths for backend OAuth 2.0 APIs. Define what support for credentials and the credentials manager must cover, including how client secrets are supplied without committing them to YAML or source control.

Written by the indexing model from the issue text.

Description

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

Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.