docs: access management guide#29
Conversation
ReviewMust-fix (2)
Suggestions (3)
|
Additional suggestion: make principal type table more explicitThe current table doesn't make it easy to distinguish user vs canister principals. Since they look similar as opaque text, consider adding a format column:
This helps developers who need to distinguish caller types in their access control logic. |
- Add missing Runtime import in controller checks Motoko snippet - Expand principal types table with format column and -cai suffix - Add note about Rust #[init] owner pattern vs Motoko shared(msg) - Add note about Rust controller checks requiring management canister - Fix Upstream comment format (em dash, add icskills source)
|
Feedback addressed:
|
Summary
guardattribute pattern for declarative access controlicp canister settings updatecanister_inspect_messagewith clear warnings about its limitationswhoamiendpoint patternSync recommendation
informed by dfinity/portal — docs/building-apps/best-practices/general.mdx+canister-securityicskill