Skip to content
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.

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

Missing list permission on keyvault leads to 502.5 error #1

Open
mattdufeu opened this issue Dec 17, 2018 · 0 comments · May be fixed by #2
Open

Missing list permission on keyvault leads to 502.5 error #1

mattdufeu opened this issue Dec 17, 2018 · 0 comments · May be fixed by #2

Comments

@mattdufeu
Copy link

mattdufeu commented Dec 17, 2018

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Unfortunately, I think it's the very last step

Any log messages given by the failure

502.5 Process Failure when browsing to the URL of the app. When looking in the Diagnostic Console, I get this exception when trying to run the app:

D:\home\site\wwwroot>dotnet .\key-vault-dotnet-core-quickstart.dll

Unhandled Exception: Microsoft.Azure.KeyVault.Models.KeyVaultErrorException: Operation returned an invalid status code 'Forbidden'

Expected/desired behavior

I'm able to browse to the about page of the app

OS and Version?

Azure (Windows 10 local but doubt that matters)

Versions

Mention any other details that might be useful

I think it's to do with permissions on the Key Vault. If I add the list permission instead of just get, it works, i.e.

    az keyvault set-policy --name '<YourKeyVaultName>' --object-id <PrincipalId> --secret-permissions get list

I'll create a PR for this, presuming it's correct.

@mattdufeu mattdufeu linked a pull request Dec 17, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant