microsoft / microsoft/azure-tools-for-java
IntelliJ Cannot create secret in Key Vault with RBAC mode
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
Creating a Secret on Key Vault directly in IntelliJ fails.
Does not matter if I am logged in with Azure CLI or OAuth 2.0
Azure: Failed to create new secret (test--application-name--password) in Key Vault (my-key-vault). Failed to create secret test--application-name--password, access denied, please make sure that you have access policy defined to do this operation.
I am fully able to create a Secret using the Azure CLI with this logged in user:
az keyvault secret set --vault-name <VAULT_NAME> --name "<NAME>" --value "<VALUE>" --content-type "password"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing secret creation from IntelliJ against a Key Vault using RBAC mode, then compare the authentication and authorization path with the working Azure CLI command. Done means an authenticated user with sufficient RBAC permissions can create the secret from IntelliJ without the access-policy error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100