Skip to content

Sign in & see your documents

This page gets you from zero to searching the corporate knowledge base in the web UI, in about 2 minutes. To connect an AI tool (Claude, Cursor, Codex) instead, see Connect your AI tool.

The public wiki you may be reading needs no account. Sign-in is only required for the app itself — search, the doc graph, context packs, and the Tokens page. See Public vs. signed-in.

The one thing to understand first: two different tokens

Almost every "I can't see anything" problem comes from confusing these:

What it is What it's for
Lantern login who you are in Lantern — email+password, or your Atlassian PAT logs you in, starts your session
Atlassian PAT a token you generate inside Confluence / Jira lets Lantern show you only the docs your Atlassian account can read (and edit them)

You always end up giving Lantern your Atlassian PAT — that is what scopes search to your permissions. The only question is when: at login (Method A), or afterwards on the Tokens page (Method B). No PAT → empty search.

Step 1 — Sign in

Open your Lantern URL (ask your admin, e.g. https://lantern.evgeniy.online). If you're not signed in, it sends you to /login. You have two options:

Method A — Sign in with Atlassian (simplest — no Lantern password)

Use the "Sign in with Atlassian" section on the login page:

  1. Paste your Confluence PAT (and optionally your Jira PAT — see Step 2 to generate them).
  2. Click Sign in with Atlassian.

Lantern validates the PAT against Atlassian, creates your account automatically, and scopes your view to what you can read — all in one step. You're done; skip to Step 3.

Method B — Email + password

Use this if your admin gave you a Lantern account:

  1. Enter your email and password (≥ 8 chars) in the top form.
  2. Submit. The server sets an HTTP-only lantern_token session cookie (httponly, samesite=strict, secure over HTTPS, 14-day life) — the password never lingers in browser JavaScript.

A wrong email/password returns "Invalid email or password." — just retry, there's no lockout. With Method B you still need to connect your PAT once — continue to Step 2.

Step 2 — Generate your Atlassian PAT

(Skip if you already pasted it in Method A.)

A Personal Access Token (PAT) is a token you create inside Confluence / Jira that acts on your behalf with your permissions. Generate one in each product — both are a few clicks; the direct links jump straight to the page.

Confluence

  1. Open https://confluence.comfy.ua/plugins/personalaccesstokens/usertokens.action (or: avatar top-right → Settings / Profile → Personal Access Tokens).
  2. Click Create token.
  3. Name it lantern, set an expiry (e.g. 90 days).
  4. Copy the token now — it is shown once.

Jira

  1. Open https://jira.comfy.ua/secure/ViewProfile.jspa → in the left menu click Personal Access Tokens.
  2. Click Create token.
  3. Name it lantern, set an expiry (e.g. 90 days).
  4. Copy the token now — shown once.

Don't see "Personal Access Tokens"? Your Atlassian admin may have the feature disabled — ask them to enable PATs for your account.

Keep both tokens in your password manager. A PAT is a credential — never paste it into a shared chat, commit, or screenshot. Revoke any time from the same page.

Step 2b — Connect the PAT (Method B only)

If you signed in with email+password, tell Lantern your PAT once:

  1. Go to /tokens (the Tokens page).
  2. In the "Atlassian access" section, paste your Confluence PAT (and optionally Jira PAT) and click Connect.
  3. Lantern validates and stores it encrypted, then discovers what you can read. You'll see "Atlassian access connected — your documents will appear after indexing refresh."

To revoke later, the same section has Disconnect.

If you see "Atlassian PAT storage is not configured (secrets unavailable)", your admin hasn't set LANTERN_SECRET_KEY — ask them to enable it.

Step 3 — Verify you see your docs

Go to /search and search for something you know exists in Confluence or Jira (e.g. a project name, or a ticket key like CMP-1422). You should get ranked results with titles and source links.

From the API, the session cookie answers who am I:

curl -s --cookie 'lantern_token=<cookie>' https://lantern.evgeniy.online/api/v1/auth/me
# {"user_id":"...","email":"[email protected]","role":"user", ...}

"I signed in but search is empty" — why?

You only see a document if it is both:

  1. indexed — its Confluence space / Jira project is in your instance's ingest scope (an admin setting), and
  2. readable by your Atlassian PAT — your upstream permissions allow it.

So an empty search is almost always one of:

  • No PAT connected → you authenticated but Lantern can't scope your ACL. Connect it (Method A, or Step 2b). This is the #1 cause.
  • Space/project not indexed → ask your admin to add it to the ingest scope.
  • You see less than a teammate → expected; results are filtered to your upstream permissions. Lantern never shows a doc your Atlassian account can't read.

What's next?

Sign out

Use the sign-out control in the nav, or POST /api/v1/auth/logout — it clears the cookie and deletes the server-side session.