Skip to content

Sections: let course admins create their own API keys - #79

Open
pancakereport wants to merge 1 commit into
sections-single-deploymentfrom
sections-api-keys
Open

pancakereport wants to merge 1 commit into
sections-single-deploymentfrom
sections-api-keys

Conversation

@pancakereport

Copy link
Copy Markdown
Collaborator

Documents berkeley-cdss/sections#59, which fixes berkeley-cdss/sections#29: course admins now create their own per-course API keys instead of asking the maintainers for the shared secret.

Stacked on #78 (which is stacked on #76). Merge those first, and merge this after sections#59 is deployed.

Changes to the API Access section of sections.md

  • Removes "contact the maintainers" and the shared secret from the example.
  • Creating an API key: the steps on the Admin page's API Keys tab, and what a key can and can't do:
    • it works only in its own course, while you're an admin there
    • it stops working after 7 days without logging in to Sections
    • it can act as you or as anyone in the course
    • it can't manage keys
  • Revoking and rotating keys: any admin can revoke any key in the course; owners can rotate their own.
  • Making requests: the Authorization: Bearer header, the optional email, the response shape, and the rate limit on failed attempts.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant