feat: Adding bearer token

[aminoacidity]

Summary

Add dedicated Bearer token authentication field for HTTP monitors. Previously users had to manually add
Authorization: Bearer <token> as a custom header — this adds a first-class masked input.

Changes:

• New bearer_token column on monitor table (knex migration)
• Server-side: construct Authorization: Bearer <token> header when auth_method === "bearer"
• Frontend: "Bearer Token" option in auth method dropdown for HTTP/KW, WebSocket, and Globalping monitors, with masked
  HiddenInput for the token

Resolves #3963

Please follow this checklist to avoid unnecessary back and forth (click to expand)

• ⚠️ If there are Breaking change (a fix or feature that alters existing functionality in a way that could cause issues) I have called them out
• 🧠 I have disclosed any use of LLMs/AI in this contribution and reviewed all generated content.
  I understand that I am responsible for and able to explain every line of code I submit.
• 🔍 Any UI changes adhere to visual style of this project.
• 🛠️ I have self-reviewed and self-tested my code to ensure it works as expected.
• 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
• 🤖 I added or updated automated tests where appropriate.
• 📄 Documentation updates are included (if applicable).
• 🧰 Dependency updates are listed and explained.
• ⚠️ CI passes and is green.

Screenshots for Visual Changes

[github-actions]

Hello and thanks for lending a paw to Uptime Kuma! 🐻👋
As this is your first contribution, please be sure to check out our Pull Request guidelines.
In particular: - Mark your PR as Draft while you’re still making changes - Mark it as Ready for review once it’s fully ready
If you have any design or process questions, feel free to ask them right here in this pull request - unclear documentation is a bug too.

[aminoacidity]

thanks for guidance. have made the changes based on similar pattern.

[CommanderStorm]

I am assuming this is done despite it not having been out of draft.
LGTM, thanks

[Copilot]

Pull request overview

Adds first-class Bearer token authentication for monitors by introducing a dedicated bearer_token field, wiring it into request header construction, and exposing a masked token input in the monitor editor UI.

Changes:

• Add bearer_token column to the monitor table via a Knex migration.
• Backend: include Authorization: Bearer <token> when auth_method === "bearer" for HTTP/keyword/json-query checks and Globalping.
• Frontend: add “Bearer Token” auth method option and a masked HiddenInput bound to monitor.bearer_token.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/pages/EditMonitor.vue	Adds “Bearer Token” auth option and masked token input for multiple monitor types.
src/lang/en.json	Adds i18n string for “Bearer Token”.
server/server.js	Persists bearer_token from incoming monitor payloads.
server/monitor-types/globalping.js	Adds Bearer header generation and merges it into request headers.
server/model/monitor.js	Adds Bearer header construction for HTTP/keyword/json-query monitor requests.
db/knex_migrations/2026-05-20-0000-add-bearer-token.js	Introduces the new DB column via migration.

Comments suppressed due to low confidence (2)

server/model/monitor.js:487

• Test coverage: bearer auth is new behavior in the HTTP check path, but there are no unit tests asserting the header is constructed correctly (and omitted for empty tokens) and how it interacts with custom monitor.headers (override order). Please add/extend backend tests for the Monitor HTTP request options to cover auth_method === "bearer".

                    // Bearer token auth
                    let bearerAuthHeader = {};
                    if (this.auth_method === "bearer") {
                        bearerAuthHeader = {
                            Authorization: "Bearer " + this.bearer_token,
                        };
                    }

server/monitor-types/globalping.js:568

• getBearerAuthHeader() unconditionally returns Authorization: "Bearer " + monitor.bearer_token when auth_method === "bearer". If bearer_token is missing/empty, this produces Bearer undefined/Bearer and will send a broken auth header. Please guard for a non-empty token and return {} otherwise (or treat it as a configuration error).

    getBearerAuthHeader(monitor) {
        if (monitor.auth_method !== "bearer") {
            return {};
        }

        return {
            Authorization: "Bearer " + monitor.bearer_token,
        };

[aminoacidity]

I am assuming this is done despite it not having been out of draft. LGTM, thanks

@CommanderStorm - The first contribution document said that we should'nt change from draft unless all steps are passed. On my end it showed that it was pending approval workflow and also the auto test steps were queued up and not run sucess. But yet, all changes were done and tested.

[github-actions]

@aminoacidity congrats on your first contribution to Uptime Kuma! 🐻
We hope you enjoy contributing to our project and look forward to seeing more of your work in the future! If you want to see your contribution in action, please see our nightly builds here.

[CommanderStorm]

Nah, this is neither a "major feature", nor a significant change.

But Copilot had good suggestions..
Could you maybe do a PR to fix the websocket monitor bug?

[aminoacidity]

Nah, this is neither a "major feature", nor a significant change.

But Copilot had good suggestions.. Could you maybe do a PR to fix the websocket monitor bug?

Yes, saw that. Just submittng the PR for the ws portion.