[jposluns]

TODO Priority 2 row 1.292: authentication.md's cloudflare-access claim and rule 6, which it summarizes.

• Login options: cites Cloudflare's One-time PIN page (OTP to approved email addresses as an alternative to an identity provider, configurable alongside one), the identity-provider overview (integrating one or several providers) and the generic OIDC connector page, at the cloudflare-docs commit c896795b the guide already cites.
• Scope: the guide already limited this to a self-hosted web application; it now adds "published through Access", which the already-cited self-hosted application page shows, and states that use with any application unchanged is not established (labelled as this guide's assessment; no application-compatibility list is cited). Round 1: this description and the CHANGELOG bullet are corrected; the first version wrongly described the base as claiming any application.
• Existing instructions (create the Access application before the tunnel route; origin TLS verification and Access JWT checking for Tunnel) are kept. No command changes. The front-matter checked date advances to 2026-10-19. TODO row 1.292 moves to DONE.
• VERSION and plugin/plugin.json 1.0.692; CHANGELOG entry under 2026-10-19; generated files rebuilt.

Local checks run by the integrator on this head (pinned markdown-it-py 4.2.0): tools/run_all_checks.sh passed (All gates passed.).

[cloudflare-workers-and-pages]

Deploying secureconfig with    Cloudflare Pages

Latest commit:	272429a
Status:	✅  Deploy successful!
Preview URL:	https://89edf05c.secureconfig.pages.dev
Branch Preview URL:	https://content-authentication-cloud.secureconfig.pages.dev

View logs