{"version":"2.1.251","anchor":"remote-bridge-owner-pinning-now-reports-why-it-declined","canonical_anchor":"remote-bridge-owner-pinning-now-reports-why-it-declined","heading":"Remote bridge owner pinning now reports why it declined","tier":"internal","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/remote-bridge-owner-pinning-now-reports-why-it-declined","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Remote bridge owner pinning now reports why it declined\n\nWhen bridge owner pinning refuses a session it now reports the reason.\n\n**What**\n\nThe check that pins a remote bridge session to the credential owner can now be handed a preset owner and returns both a decision and a reason, where it previously just returned nothing on failure. Reasons include no token, disabled, not a store login, not the owner, unresolved, and no identity.\n\n**Details**\n\n- The returned pin also exposes a way to ask whether the owner was verified.\n- Some paths report unresolved rather than performing a lookup, so the outcome depends on which checks the session start runs.\n\n**Evidence**\n\n`not_store_login`\n\n- Area: Remote Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}