IPC scope API changes
The scope::ipc::RemoteDomainAccessScope methods enable_tauri_api and enables_tauri_api were removed. Instead, enable core plugins individually via scope::ipc::RemoteDomainAccessScope::add_plugin.
Tauri · Plugins and security · all subjects
permissions & capability model
7 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
IPC scope type changes
In Tauri 2.0, scope::IpcScope was removed and replaced with scope::ipc::Scope.
File system scope type changes
In Tauri 2.0, scope::FsScope, scope::GlobPattern, and scope::FsScopeEvent were removed. Use scope::fs::Scope, scope::fs::Pattern, and scope::fs::Event instead.
Permission system migration in Tauri v2
The v1 permission allowlist was completely rewritten to a new permission system. The new system works like an ACL (Access Control List) and allows permission/denial of commands, assignment of permissions to specific windows and domains, and definition of access scope. Capability files are created in src-tauri/capabilities folder and the migrate CLI command automatically converts v1 permissions.
Capability files in Tauri v2
In Tauri 2.0, app permissions are configured by creating capability files in the src-tauri/capabilities folder. Tauri automatically sets up everything else.
Core plugin permission identifiers require core: prefix in Tauri 2.0
When migrating from Tauri 2.0 beta to release candidate, all core permission identifiers in capabilities must be prefixed with 'core:'. For example, 'path:default' becomes 'core:path:default', 'event:default' becomes 'core:event:default', 'window:default' becomes 'core:window:default', 'app:default' becomes 'core:app:default', 'image:default' becomes 'core:image:default', 'resources:default' becomes 'core:resources:default', 'menu:default' becomes 'core:menu:default', and 'tray:default' becomes 'core:tray:default'.
Core:default permission simplifies core plugin permissions
A new special 'core:default' permission set was added that includes all default permissions for all core plugins, allowing simplification of permission declarations in capability configurations by using a single 'core:default' permission instead of listing individual core plugin permissions.