Skip to content

added: new azure dev ops credential types #1788

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

added: new azure dev ops credential types #1788

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions docs/console/company-configuration/providers/api-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,14 +178,16 @@ curl --location --request POST 'https://console-url/api/backend/tenants/my-examp
</details>

:::info Supported credential types
As discussed [here](/console/company-configuration/providers/configure-provider.mdx#step-3-credentials), different types of providers support different types of credentials. The following table shows the credential types supported by each provider, referring to the data model shown above:
As discussed [here](/console/company-configuration/providers/configure-provider.mdx#step-3-credentials),
different types of providers support different types of credentials.
The following table shows the credential types supported by each provider, referring to the data model shown above:

| Credentials Type | Providers |
| ------------------ |:---------------------------------------------------------------------:|
| token | gitlab, github, bitbucket, azure-devops, vault, jenkins |
| m2m | vault |
| client_credentials | jenkins |
:::
| client_credentials | jenkins, azure-devops |
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to add from what version of 13.X.X will this feature be added?


:::caution Data model update
The fields `capabilities` and `expirationDate` (within `credentials`) have been introduced starting from version 10.8 of the Console.
:::
Expand Down Expand Up @@ -321,6 +323,7 @@ Examples of request bodies specific to each provider type are shown below. In th
</Tabs>

### PATCH

To edit an existing provider, you need to call the respective API as follows:

```sh
Expand Down
6 changes: 3 additions & 3 deletions docs/console/company-configuration/providers/configure-provider.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,11 +195,11 @@ Credentials entered at this stage, for security reasons, will never again be sho
Depending on the provider selected in step 1, the types of credentials supported will change. The following table shows the credential types supported by each provider:

| Credentials Type | Providers |
| ------------------------------ |:------------------------------------------------------------------------:|
| ------------------------------ | ------------------------------------------------------------------------ |
| Token | GitLab, GitHub, Bitbucket, Azure DevOps, Vault, Jenkins, Azure Key Vault |
| M2M | Vault |
| Client Credentials | Azure Key Vault,Jenkins |
| Client Credentials Certificate | Azure Key Vault |
| Client Credentials | Azure Key Vault, Jenkins, Azure DevOps |
| Client Credentials Certificate | Azure Key Vault, Azure DevOps |

:::caution Assign the right scope to your credentials
Make sure, when generating credentials on the respective provider sites, to assign them a scope so that they have the necessary permissions for all read and write operations performed through the Console.
Expand Down