Azure / Azure/azure-rest-api-specs-examples
Reader role does not have access to call NewBackupStatusClient().Get
- Dominant language
- No language data
- Stars
- 40
- Forks
- 23
- Avg merge
- 23h 36m
- Merged PRs (30d)
- 172
Description
### Link to sample
https://learn.microsoft.com/en-us/rest/api/backup/backup-status/get?view=rest-backup-2023-02-01&tabs=Go
### Library name and version
armrecoveryservicesbackup/v2
### Language of the Sample
- [ ] C#/.NET
- [ ] Java
- [ ] JavaScript/TypedScript
- [ ] Python
- [X] Golang
- [ ] Other - Please specify in Issue details field
### Sample Issue Type
- [X] Sample not working
- [ ] Sample missing
- [ ] Do not understand sample
### Issue details
RBAC Reader role does not have access to call NewBackupStatusClient().Get. Backup Reader role works.
### Expected behavior
Reader role should contain all other reader roles
### Actual behavior
NewBackupStatusClient().Get returns RESPONSE 403: 403 Forbidden ERROR CODE: AuthorizationFailed when accessed using a service principal with Reader role
### Reproduction Steps
Run the example code with a service principal with Reader role
### Environment
Multiple environments
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Go sample for NewBackupStatusClient().Get and reproduce it using a service principal assigned the Reader role. Compare the 403 AuthorizationFailed response with the same call under Backup Reader, then verify whether the expected fix is a sample change or a correction to the Azure RBAC permissions; done means the documented Reader-role behavior matches the actual result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100