docs: unlisted auth schemes pass through on coordinators without SSO

[as51340]

Release note

On a high availability coordinator, a Bolt authentication scheme that is not listed in --auth-module-mappings now takes the same passthrough path as basic/none instead of being rejected as unsupported. With no SSO module configured it is accepted with credentials ignored (the 3.12 behavior); once SSO is configured it is denied under the same license and writable-role conditions as basic auth, with a message naming the scheme.

Documented on the coordinator authentication page:

• Rewrote Authentication modes as a two-path rule (listed SSO scheme vs. everything else) and dropped the standalone "unsupported scheme" rejection.
• Renamed Basic authentication passthrough to Authentication passthrough and extended it to unlisted schemes, with both denial messages and a 3.13 → 3.14 callout.
• Generalized the break-glass, license-loss, and follower-without-quorum sections from "basic auth" to "passthrough".
• Small wording alignment for SHOW CURRENT USER / SHOW CURRENT ROLE on the HA commands reference.

Related product PRs

• fix: Pass unlisted auth schemes through on coordinators without SSO memgraph#4962

Checklist:

• Add appropriate milestone (current release cycle)
• Add bugfix or feature label, based on the product PR type you're documenting
• Make sure all relevant tech details are documented
  • Update reference pages (no flag, clause or function changes)
  • Search for the feature you are working on (mentions) and make updates if needed
  • Provide a basic example of usage
  • In case your feature is an Enterprise one, list it under ME page and mark its page with Enterprise (page already marked Enterprise)
• Check all content with Grammarly
• Perform a self-review of my code
• The build passes locally
• My changes generate no new warnings or errors

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Sep 29, 2026 9:39am UTC