Approaches for tenant-specific secrets?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Just curious if there is guidance on tenant-specific secrets while using this approach? If we went this route, we'd continue using Auth0 for tenant-specific logins (with nextjs-auth0), and that requires a few secrets per tenant.
The two thoughts that come immediately to mind are:
- HCP Vault Secrets (prefixed by the subdomain like the other values in Redis)
- Keeping an encryption key in a Sensitive Environment Variable and encrypting ourselves before storing in Redis
The second would require a bit more code, but I'm guessing would be cheaper and have less latency?
Any thoughts?
Contributor guide
No contributing guide indexed for this repository
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 file, test, or entry point is identified. The issue is an unanswered design question about handling tenant-specific Auth0 secrets with HCP Vault Secrets or encrypted Redis values. Work would require a decided approach, defined implementation scope, and an agreed validation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, redis
- Domain
- authentication, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100