Skip to content

API key scope catalog: derive from routes and expose for key-creation UX #615

Closed

Description

@robertocarlous

Context

src/auth/scopes.ts and src/middleware/adminAuth.ts define scopes (e.g. portfolio:read, goals:write, recurring_deposits:write, strategies:write, webhooks:manage, vault:write, alerts:manage, fiat:write — seen in scope-denied logs). The catalog is code-only.

Proposal

  • Export a machine-readable scope catalog (name, description, risk level, endpoints covered)
  • Admin API GET /api/admin/keys/scopes for the key-creation UI
  • Test that every requireApiKeyScope/requireAdminScope call site references a catalog entry (no ad-hoc strings)

Acceptance criteria

  • Catalog generated or validated in CI
  • Docs list all scopes with descriptions

Activity

  1. ranjeetprabhatedu-dotcom commented on Oct 19, 2026

    @ranjeetprabhatedu-dotcom

    Hello maintainers,

    I reviewed "API key scope catalog: derive from routes and expose for key-creation UX" and would like to work on this.

    I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.

    I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.

    Thank you!

  2. bitech026 commented on Oct 19, 2026

    @bitech026

    @bitech026 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I am very interested in taking on this issue because I've worked on similar tasks before, I am available to start immediately

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @bitech026 to this issue.

  3. Dev-Dare4 commented on Oct 19, 2026

    @Dev-Dare4

    @Dev-Dare4 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Kindly assign this issue to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dev-Dare4 to this issue.

  4. johnsmccain commented on Oct 19, 2026

    @johnsmccain
    Contributor

    @johnsmccain has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainers, I would like to express my interest in working on this issue. I have reviewed the issue description and understand the problem that needs to be addressed. My approach will be to investigate the existing codebase, identify the root cause, and implement a solution that follows the project's existing architecture and coding standards.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @johnsmccain to this issue.

  5. Wittig18 commented on Oct 19, 2026

    @Wittig18

    @Wittig18 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    hey maintainer, i would love to work on this

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Wittig18 to this issue.

  6. drips-wave commented on Oct 19, 2026

    @drips-wave

    Congratulations, @johnsmccain! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @johnsmccain: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  7. grantfox-oss commented on Oct 19, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @johnsmccain's PR #628 was approved and merged by @robertocarlous.

    🏆 @johnsmccain: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (879 total points). Track your full progress on GrantFox.

    👏 Great work, @johnsmccain! Keep contributing to Neurowealth.

  8. added a commit that references this issue on Oct 19, 2026
  9. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @johnsmccain as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @johnsmccain: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions