dapr / dapr/components-contrib

Support for appRole based authentication for secretstores.hashicorp.vault

Open
#2,231 6 comments 1 reaction 0 assignees View on GitHub
good first issue kind/enhancement pinned
Dominant language
Go
Stars
602
Forks
580
Avg merge
4d 9h
Merged PRs (30d)
6

Description

## Describe the feature

We use AppRole based authentication to manage secrets within Vault. More info on AppRole can be found [here](https://developer.hashicorp.com/vault/docs/auth/approle).

DAPR's secretstores.hashicorp.vault Component uses Token based authentication. Here are the key/values on the Component that requires to provide the token

```
- name: vaultTokenMountPath # Required if vaultToken not provided. Path to token file.
value : "[path_to_file_containing_token]"
- name: vaultToken # Required if vaultTokenMountPath not provided. Token value.
value : "[path_to_file_containing_token]"
```

The apps don't have access to the token, however they are designed to access Vault with AppRole authentication. So the ask here is to support AppRole based authentication from DAPR's Component when spec.type=secretstores.hashicorp.vault

## Release Note

RELEASE NOTE:

Contributor guide

Open the contributing guide

Research direction

Start with the secretstores.hashicorp.vault component and its spec.type=secretstores.hashicorp.vault configuration, then read the linked HashiCorp AppRole documentation alongside the existing vaultToken and vaultTokenMountPath settings. Done means the component supports AppRole-based authentication with a clearly documented configuration and verified behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.