Admins can block plugins and marketplaces from unlisted sources, with refusals naming the policy.
What's wrong with this entry?
Administrator-managed settings can now block plugins and marketplaces whose entry source is not listed in the managed extraKnownMarketplaces policy, so install, update and refresh stop with a policy error instead of running that entry's command for minting auth headers. Refusals are reported separately from ordinary failures, and the messages name the policy rather than looking like a network or catalog fault. Nothing is blocked unless the managed policy sets disableCommandPluginSources or allowManagedHooksOnly; without those, behaviour is unchanged.
- A blocked marketplace update reports
<name> marketplace not updated (managed policy) — ask your adminand lists the sources that were refused. - The plugin update path explains that
your organization's managed settings forbid its headersHelper (the version shown is from the cached catalog; ask your admin), so the displayed version may be stale. - Each refusal is classified as either "lockdown", meaning the policy forbids the source outright, or "remote_policy_unconsented", meaning a remote source whose policy has not been consented to in the current remote session.
- Two new diagnostic kinds carry these refusals, including an
autoupdate-disabled-by-policynotice. - Refused marketplaces are gathered into their own list during refresh rather than folded in with genuine failures.
headersHelper, the command that supplies auth headers for a source, is now accepted on plugin entries declared in settings files as well as on marketplace entries, and a validator rejects values that are over-long or contain non-printable ASCII.- The message for an inactive plugin no longer says "or blocked by policy" and now states only that the plugin is disabled.
autoupdate-disabled-by-policy, not updated (managed policy), your organization's managed settings forbid its headersHelper (the version shown is from the cached catalog; ask your admin)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Managed setting to block command-sourced plugins
Both mention disable command source allow managed hook only
-
v2.1.229
Plugins can be installed from a command that produces the plugin directory
Both mention disable command source allow managed hook only
-
v2.1.229
Marketplaces can ship a plugin built by running a local command
Both mention disable command source allow managed hook only