Skip to content

1.8.0 changelog intro + SESSION_SECRET how-to #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
demigodmode wants to merge 1 commit into
base: main
Choose a base branch
from
Open

1.8.0 changelog intro + SESSION_SECRET how-to #340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [1.8.0] - 2026-11-08

OneSearch isn't single-user anymore. You can add more people as admins or members, everyone gets their own sign-in and API tokens, and admins get an audit log of who did what.

If `SESSION_SECRET` is set, upgrading from 1.7.x needs no extra steps. If it isn't, everyone gets signed out once. To set it, generate a key with `openssl rand -base64 32` and add `SESSION_SECRET=<that key>` to your `.env` ([details](https://onesearch.readthedocs.io/en/latest/configuration/environment-variables/#authentication)). See also the [1.8.0 upgrade notes](https://onesearch.readthedocs.io/en/latest/getting-started/upgrading/#upgrading-to-180).

### Added

- Several user accounts. Each user is an admin or a member. Admins add users on **Admin > Users** with a temporary password, and the new user picks their own password at first sign-in. Admins can change roles, disable and re-enable accounts, reset passwords and delete users. Nobody can disable, demote or delete their own account, and the last active admin can't be removed.
- User accounts, each one an admin or a member. Admins add users on **Admin > Users** with a temporary password, and the new user picks their own password at first sign-in. Admins can change roles, disable and re-enable accounts, reset passwords and delete users. Nobody can disable, demote or delete their own account, and the last active admin can't be removed.
- Members can search, open, preview and download documents. They don't see Sources, Status, Agents, Settings, Users or Audit log.
- An Account page for every user, with password change and API tokens.
- API tokens for scripts and other apps. They start with `os_`, can expire after 30 days, 90 days, a year, or never, and can only search and open documents. `onesearch login --token` and `ONESEARCH_TOKEN` accept them for `onesearch search`. Admins can see and revoke any user's tokens.
Expand All @@ -22,7 +26,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Sessions and download links end right away when a user's role or status changes or an admin resets their password. Changing your own password ends your other sessions.
- The gear icon in the header now opens Account for everyone. Admins see the admin pages listed under it, and members get a Settings page with the Appearance and Search options, saved in their browser.
- Long text pages have Previous/Next under the text as well as above it.
- The Metadata card on document pages starts collapsed.
- The Metadata card on a file's page starts collapsed.

### Fixed

Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/upgrading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ There is no major-only tag like `1`.

Nothing to set up. Pull the new image and restart as usual.

Startup runs a migration that adds user roles, API tokens and the audit log. The account you set up becomes an admin, and it's the only account there is until you add more from **Settings > Users**. Sessions you already have keep working until they expire. The exception is installs that never set `SESSION_SECRET`: they get signed out once, because the key they used before was a built-in one that is now replaced. Setting `SESSION_SECRET` avoids that on future upgrades.
Startup runs a migration that adds user roles, API tokens and the audit log. The account you set up becomes an admin, and it's the only account there is until you add more from **Settings > Users**. Sessions you already have keep working until they expire. The exception is installs that never set `SESSION_SECRET`: they get signed out once, because the key they used before was a built-in one that is now replaced. Setting `SESSION_SECRET` avoids that on future upgrades: generate a key with `openssl rand -base64 32`, add `SESSION_SECRET=<that key>` to your `.env`, and restart. See [Authentication](../configuration/environment-variables.md#authentication) for more.

@coderabbitai coderabbitai Bot Nov 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor · Functional Correctness · Quick win

Recreate the container after changing .env.

If an operator uses docker compose restart, the container keeps its old environment, so SESSION_SECRET remains unset. Specify docker compose up -d instead, using the applicable Compose file. (docs.docker.com)

Minor · Functional Correctness · Quick win

Warn that setting a new secret ends current sessions.

If users sign in after the upgrade and then follow this instruction, the new key replaces the generated key and signs them out again. Recommend setting the secret before upgrading, or warn about the second sign-out. (raw.githubusercontent.com)


Code files that start with a docstring or comment get a cleaner title now. Files that are already indexed keep their old title until you run a full reindex on their source.

Expand Down
Loading