[stub] document nested impersonation public API
Open
Nobody has claimed this yet.
chore
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
i.e. we use the original-user-info.impersonation-proxy.concierge.pinniped.dev extra key to store the original user as JSON blob of ${some_struct}.
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
Start by locating the public API definition for nested impersonation and the handling of the original-user-info.impersonation-proxy.concierge.pinniped.dev extra key. Document the original user’s JSON representation and the nested impersonation behavior, then verify that the public API description matches the implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100