* Flesh out 229b what/why
* Adjust approvers
* Behaviour
* A treatise on the wrong way of doing things
* More headers/thinking on the user journey
* Cross-scope privileges
* Sub-pinnign of output credentials
* Start to consider "The form of Scoped Bots"
* ADd notes on ScopedBot
* Few more notes on form of scoped bot
* Take an opinionated stance on behaviour
* Eliminate "subkind" option from the form of scoped bots
* Start working on role assignments
* Keep hacking on behaviour
* Examine privilege further
* child -> descendent
* Rearrange
* Remove duplicate example case
* Further explain pinning
* further ismplify?
* Note on `assignable_scopes` field
* On the scoping of scoped bots - a thesis on cross-scope privilege
* Restructure
* Security concerns and the scoping of scoped bots
* Notes on name reuse
* Add another mitigation to name reuse
* Note on namespaces
* Add example config for sub-pinning
* Maybe decide on reusing existing bot for scoped rbac
* Write up "Joining" implementation details
* Add note on scope
* wip progress on bot resource
* Add explicit remark on why the constraint of bot access to scope of
oriign exists
* Add explanation of why no unscoped roles
* Security considerations wip
* bot -> mwi
* Extending list rpc with by scope filtering
* note on scope transitions
* Expand Future Improvements: B.2 Cross-scope privileges
* Add WIPs for certificate issaunce and `tbot`
* Summarise current state of bot certificate issuance
* Clarify who invokes rpc
* add descriptive wips
* Add example configuration
* wip remarks on mode field
* Add implementation phases section
* Add WIP for SRA/Bot Instances
* reshuffle
* Add ScopedRoleAssignment impl notes
* ADd remark on safe to ignore as striclty decreases privileges
* calculating scoped role assignments
* Confused deputy attack
* Add note to future improvements
* Expound the details of bot identity today
* Remove wip header from implementation details
* rename/relink section on encoding/calculating privilege for scoped bots
* Remark on namespacing
* Update example SRA to use bot field
* Simplify by using `assigned_scope` rather than `scope` for joining
restrictions
* readnosecrets
* Clarify choice re: scoped bot binding
* Add remarks/description of bot_scope field
* Scoped bot field enumeration testing
* Add outcome to security concern re: traits
* Outline implementation plan
* Fix numbering
* Allow scoped role assignment scope of origin above bot scope
* Add notes on prohibiting spec.traits for scoped bot
* Muse more on certs/scope pinning
* Notes on BotInstances
* Add botinstances to implementation phases
* Highlight need to test invariants
* Remark on changes to tbot
* Identity of scoped bots
* Add BotInternal certificate attribute
* Simplify sentence
* Update joining with answered questions
* Qualify that bot_scope must match scope of bot
* unwip implementation phases
* Update scoped_token example
* Update link
* fix line wrapping
* E2E testing
* bot -> bot_name in SRA
* Remark on "explicit scope in references" security control
* Security considerations
* ux
* spag
* SPAG
Co-authored-by: rosstimothy <[email protected]>
* Fix old reference to assigned_scope found by codex
* Update product reviewer
* Update rfd/0229b-mwi-scopes.md
* Update rfd/0229b-mwi-scopes.md
* Update rfd/0229b-mwi-scopes.md
* remove refernece to socpe of origin
* notes on access lists
* Apply suggestions from code review
Co-authored-by: Tim Buckley <[email protected]>
* Update rfd/0229b-mwi-scopes.md
Co-authored-by: Tim Buckley <[email protected]>
* Move some checks from apply-time to issuance-time
* Address `usage_mode` field for non bot join tokens
---------
Co-authored-by: rosstimothy <[email protected]>
Co-authored-by: Tim Buckley <[email protected]>
Co-authored-by: Tim Buckley <[email protected]>
