Skip to content

Add 1Password extension policy configuration#1708

Merged
dhh merged 3 commits intobasecamp:devfrom
hjanuschka:1password-extension
Sep 17, 2025
Merged

Add 1Password extension policy configuration#1708
dhh merged 3 commits intobasecamp:devfrom
hjanuschka:1password-extension

Conversation

@hjanuschka
Copy link
Copy Markdown
Contributor

Summary

  • Added 1Password browser extension policy configuration for Chromium and Brave browsers
  • Created migration script to install the policies during system setup

Changes

  • Added static/onepassword.json with 1Password extension ID and installation policies
  • Created migration 1757683389.sh to:
    • Create policy directories for both Chromium (/etc/chromium/policies/managed/) and Brave (/etc/brave/policies/managed/)
    • Copy the policy file to both browser policy directories
    • Set appropriate permissions (755 for directories, 644 for policy files)

Test plan

  • Run the migration script on a test system
  • Verify directories are created with correct permissions
  • Confirm 1Password extension is automatically installed in Chromium
  • Confirm 1Password extension is automatically installed in Brave

@markstos
Copy link
Copy Markdown

Why force 1Password extension to be installed when not everyone uses 1Password?

- Added policy files in config/chromium/policies/managed/ and config/brave/policies/managed/
- Created migration to copy policies to system directories /etc/chromium and /etc/brave
@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

The default install of Omarchy is my setup. It is and should be possible to remove anything and everything after you're up and running, but we start from the base of "this is what I use". You can read more about the principles powering Omarchy here: https://learn.omacom.io/3/omacom/76/omakase-computing

@dhh dhh changed the base branch from master to dev September 17, 2025 07:53
@dhh dhh merged commit b5b4dea into basecamp:dev Sep 17, 2025
@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

@hjanuschka This isn't actually working. The extension is not getting installed on a new setup.

@hjanuschka
Copy link
Copy Markdown
Contributor Author

hjanuschka commented Sep 17, 2025

you removed the migration, it needs to copy the onepassword.json to /etc/chromium/.....
have found no other way to put it outside the repo into /etc/

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

This was on a fresh installation. Those files are copied over automatically.

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

My bad. They weren't copied to the right place!

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

Now that it's in the right place, the machine just locks up when you boot chromium:

image

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

It starts on the second launch, but the 1pw extension is not installed.

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

@hjanuschka
Copy link
Copy Markdown
Contributor Author

gosh! sorry! will try this, can we revert that in dev branch?

using a VM (with iso) is the fastest way to debug/try fresh install?

@hjanuschka
Copy link
Copy Markdown
Contributor Author

initially when i did the PR - had browser running, copied file over there, it showed up in chrome://policy and installed extension - strange

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

Yeah, fastest way to test fresh install is by running ./bin/omarchy-iso-make-dev from https://github.com/omacom-io/omarchy-iso

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

Hmm. I can get it working just fine in proxmox. Must be an issue with the qemu flow. Everything is working now 😄

@dhh
Copy link
Copy Markdown
Member

dhh commented Sep 17, 2025

Hmm, no, this isn't going to work, since folks can't remove the extension then:

image

hamidriaz1998 pushed a commit to hamidriaz1998/omarchy that referenced this pull request Sep 18, 2025
* Add 1Password extension policy configuration for Chromium and Brave

- Added policy files in config/chromium/policies/managed/ and config/brave/policies/managed/
- Created migration to copy policies to system directories /etc/chromium and /etc/brave

* I don't want to push it into existing installations at the moment

We just leave it for new installs

---------

Co-authored-by: David Heinemeier Hansson <david@hey.com>
dhcrzf pushed a commit to dhcrzf/omarchy that referenced this pull request Sep 18, 2025
* Add 1Password extension policy configuration for Chromium and Brave

- Added policy files in config/chromium/policies/managed/ and config/brave/policies/managed/
- Created migration to copy policies to system directories /etc/chromium and /etc/brave

* I don't want to push it into existing installations at the moment

We just leave it for new installs

---------

Co-authored-by: David Heinemeier Hansson <david@hey.com>
MarianoMiguel pushed a commit to MarianoMiguel/omarchy that referenced this pull request Sep 18, 2025
* Add 1Password extension policy configuration for Chromium and Brave

- Added policy files in config/chromium/policies/managed/ and config/brave/policies/managed/
- Created migration to copy policies to system directories /etc/chromium and /etc/brave

* I don't want to push it into existing installations at the moment

We just leave it for new installs

---------

Co-authored-by: David Heinemeier Hansson <david@hey.com>
ryanrhughes pushed a commit that referenced this pull request Sep 19, 2025
* Add 1Password extension policy configuration for Chromium and Brave

- Added policy files in config/chromium/policies/managed/ and config/brave/policies/managed/
- Created migration to copy policies to system directories /etc/chromium and /etc/brave

* I don't want to push it into existing installations at the moment

We just leave it for new installs

---------

Co-authored-by: David Heinemeier Hansson <david@hey.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants