-
-
Notifications
You must be signed in to change notification settings - Fork 2
token permissions
PSRule.Rules.AzureDevOps requires a personal access token with the appropriate permissions to export data from Azure DevOps. When running PSRule.Rules.AzureDevOps you can choose 3 different token types:
- FullAccess: Allows for full access to Azure DevOps, use with caution
- FineGrained: Allows for fine-grained access to Azure DevOps, this is the recommended token type
- ReadOnly: Allows for read-only access to Azure DevOps
The FullAccess token type is the most permissive and allows for maximum rule
coverage. This token type is recommended for use with PSRule.Rules.AzureDevOps
but should be used with caution. Check your organization's security policies
before using this token type.
The FullAccess token type can be created in Azure DevOps by following these steps:
- Navigate to your Azure DevOps organization
- Select the User Settings option from the top right menu
- Select the Personal access tokens option from the menu
- Click the New Token button
- Enter a name for the token
- Select the Full access scope
- Click the Create button
- Copy the token value and store it in a secure location
- Use the token value in your pipeline
The FineGrained token type is the recommended token type for use with
PSRule.Rules.AzureDevOps. This token type allows for fine-grained access to
Azure DevOps and is the most secure token type that allows for near-maximum
rule coverage while still offering a detailed overview of the required permissions.
The FineGrained token type can be created in Azure DevOps by following these steps:
- Navigate to your Azure DevOps organization
- Select the User Settings option from the top right menu
- Select the Personal access tokens option from the menu
- Click the New Token button
- Enter a name for the token
- Select the Custom defined scope
- Select
Readfor all scopes that have aReadoption - Select
Read & Managefor all scopes that have aRead & Manageoption - Do not select any other scopes
- Click the Create button
- Copy the token value and store it in a secure location
- Use the token value in your pipeline
The ReadOnly token type is the most restrictive and allows for read-only access
to Azure DevOps. This token type is recommended for use with PSRule.Rules.AzureDevOps
when your security policies do not allow for the use of the FullAccess or FineGrained
token types.
The ReadOnly token type can be created in Azure DevOps by following these steps:
- Navigate to your Azure DevOps organization
- Select the User Settings option from the top right menu
- Select the Personal access tokens option from the menu
- Click the New Token button
- Enter a name for the token
- Select the Custom defined scope
- Select
Readfor all scopes that have aReadoption - Do not select any other scopes
- Click the Create button
- Copy the token value and store it in a secure location
- Use the token value in your pipeline
The following table lists the token scopes that are required for each command.
| Rule Function | API(s) | Version | Method | Scope(s) | PAT Category | PAT Name |
|---|---|---|---|---|---|---|
| Get-AzDevOpsProject | projects | 6.0 | GET | vso.profile | User Profile | Read |
| vso.project | Project and Team | Read | ||||
| Get-AzDevOpsPipelines | pipelines | 6.0-preview.1 | GET | vso.build | Build | Read |
| pipelines/{pipelineid} | 6.0-preview.1 | GET | vso.build | Build | Read | |
| Get-AzDevOpsPipelineAcls | accesscontrollists/{securityid} | 6.0 | GET | vso.security_manage | Security | Manage |
| Get-AzDevOpsPipelineYaml | pipelines/{pipelineid}/runs | 5.1-preview | POST | vso.build | Build | Read |
| pipelines/{pipelineid} | 7.1-preview.1 | GET | vso.build | Build | Read | |
| git/repositories/{repositoryid}/items | 6.0 | GET | vso.code | Code | Read | |
| Get-AzDevOpsEnvironments | pipelines/environments | 6.0-preview.1 | GET | vso.environment_manage | Agent Pools | Read and Manage |
| vso.build | Build | Read | ||||
| pipelines/checks/configurations | 7.2-preview.1 | GET | vso.build | Build | Read | |
| Get-AzDevOpsReleaseDefinitions | release/definitions | 7.2-preview.4 | GET | vso.release | Release | Read |
| Get-AzDevOpsReleaseDefinitionAcls | accesscontrollists/{securityid} | 6.0 | GET | vso.security_manage | Security | Manage |
| Get-AzDevOpsPipelinesSettings | build/generalsettings | 7.1-preview.1 | GET | vso.project | Build | Read |
| Get-AzDevOpsRepos | git/repositories | 6.0 | GET | vso.code | Code | Read |
| Get-AzDevOpsBranchPolicy | policy/configurations | 6.0 | GET | vso.code | Code | Read |
| Get-AzDevOpsRepositoryPipelinePermissions | pipelines/pipelinePermissions/repository | GET | vso.build | Build | Read | |
| Get-AzDevOpsRepositoryAcls | accesscontrollists/{securityid} | 6.0 | GET | vso.security_manage | Security | Manage |
| Test-AzDevOpsFileExists | git/repositories/{repositoryid}/items | 6.0 | GET | vso.code | Code | Read |
| Get-AzDevOpsRepositoryGhas | Contribution/HierarchyQuery | 5.0-preview.1 | POST | tbc | tbc | FullACcess |
| Get-AzDevOpsArmServiceConnections | serviceendpoint/endpoints | 6.0-preview.4 | GET | vso.serviceendpoint | Service Connections | Read |
| Get-AzDevOpsArmServiceConnectionChecks | bipelines/checks/configurations | 7.2-preview.1 | GET | vso.build | Build | Read |
| Get-AzDevOpsVariableGroups | distributed task/variablegroups | 7.2-preview.2 | GET | vso.variablegroups_read | Variable Groups | Read |
The following table lists the token scopes that are required for each rule.