Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Chrome passkey popup
I have this issue where Chrome's passkey popup overlays 1Password. The device is Entra joined and the passkey is bound to the device. Deleting the passkey in Windows settings is not an option. Everytime i visit a Microsoft login page the Chrome passkey popup also shows over 1Password. This only happens when using Windows 11 + Chrome. Using Windows 11 + Microsoft Edge does not show any popup from MS. 1Password is set as the default password manager in Chrome Any recommendations? 1Password Version: 8.12.10 Extension Version: 8.12.12.44 OS Version: Windows 11 25H2 | 26200.8246 Browser: Chrome 124.0.7444.163
Group Policy Intune ADMX Ingestion Error
Hi 1Password Community, We've been looking at managing 1Password policies through the generated ADMX+ADML files. The files themselves upload to Intune fine, but when the client is attempting to ingest the file(s) we receive the following error: MDM ConfigurationManager: Command failure status. Configuration Source ID: (5B33F6A6-E59D-4384-8CB2-6858C3CCF0CD), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/OnePassword82518298-c5ba-4142-b473-7d937e4105c6/Policy/OnePassword82518298-c5ba-4142-b473-7d937e4105c6), Result: (Catastrophic failure). See image 1 Originally, this was thought of as a bug as the feature was still fairly recently implemented. After a couple of months of waiting, I tried generating the files again earlier this week (currently using app version "1Password for Windows 8.11.20 (81120039)") and discovered the same error is still present. The patch notes for January 19th mention that this should have been fixed, but when trying again these past couple of days the error persisted. https://releases.1password.com/windows/stable/#1password-for-windows-8.12.0 See image 2 Doing some research, I came across the following GitHub-repo: https://github.com/Micke-K/IntuneManagement/blob/master/ADMXImport.md, which mentions that QWORD-values are unsupported and will generate a catastrophic failure on the clients - exactly the same as we've been experiencing on our clients. See image 3 Based on this revelation, I started to manually edit the ADMX and ADML-files to remove all entries for "longDecimal", which equals to these two policies: security_authenticatedUnlock_deviceBasedUnlock_askUnlockAfter security.autolock.minutes Once these entries were removed from both files and reuploaded to Intune - it started working without any further errors: ADMX Ingestion: MDM PolicyManager: ADMX Ingestion: EnrollmentId (8BE04C50-54DF-4B0D-AA1C-9A79C476C468), app name (OnePassword975d1c63-2406-4643-8f93-cb4034eb3382), setting type (Policy), unique Id (OnePassword975d1c63-2406-4643-8f93-cb4034eb3382), area (NULL). Policy Creation: MDM PolicyManager: Set policy string, Policy: (ManagedInstall), Area: (OnePassword975d1c63-2406-4643-8f93-cb4034eb3382~Policy~onepassword), EnrollmentID requesting merge: (8BE04C50-54DF-4B0D-AA1C-9A79C476C468), Current User: (Device), String: (<enabled/><data id="ManagedInstall" value="X" />), Enrollment Type: (0x6), Scope: (0x0). See image 4 and 5 As the error appears to be related to the ADMX Ingestion not being able to handle QWORD-values, the root cause of the problem may lie with Microsoft. Would it be possible from 1Passwords side to look into having the two policies be handled through either a DWORD or a String instead of a QWORD?
Edge Authentication Window when using Microsoft SSO
Hello! We have configured Microsoft/EntraID SSO for login to 1Password. The users are logged in to the Windows PC with an Active Directory User - the Users are synchronized to EntraID, where SSO with 1Password is configured. Recently we are experiencing the issue, that for every first 1Password unlock after a PC restart, when we click "Login with Microsoft" in 1Password, a Browser window opens, asking for the Microsoft 365/EntraID login credentials. The login to 1Password is successful anyway, either if we enter the credentials in this window, or if we do not enter any credentials and close the window. How can we prevent that Browser window asking for credentials? Is there something we need to configure on 1Password side? Thank you and best regards, MichaelAuto type not working on certain app after today's update to 8.12.12
We use a tool called CCH Pfx Practice Management. It was working great until today's update. I tried unchecking the auto-type box and re-checking it, but it still does not work. Our two other applications that are also from CCH and use auto-type, work just fine....so the auto-type feature is still working, just not on CCHPM. Any ideas? We also tried recreating a new login, but it did not work either. Thank you.
Sticky icon remains on other pages
Hi, Looking for advice on how to solve this issue, tried with 1Password - Password Manager > Hide on this page. That didn't change anything sadly. Only one user has this problem with one webpage where the icon from a login field remains, even when viewing other pages on the same website. The icon remains when navigating to other pages, as if the field remains hidden in the background. A refresh of the page removes the "ghost icon". Seems quite similar to another thread I found. https://www.1password.community/discussions/1password/1password-menu-icon-in-text-fields/36698Managed Update of Intune Win32 App
I deploy 1Password via Intune, and I recently transitioned our deployment from the MSI installer to the MSIX installer—as a Win32 app in both cases. I prefer to manage the deployed version and so disable Auto Update. When deploying using the MSI installer, I used a File detection rule that checked for the presence of the app and also checked the version. Rule type: File Path: C:\Program Files\1Password\app\8 File or folder: 1Password.exe Detection method: String (version) Operator: Greater than or equal to Value: 8.x.x Associated with a 32-bit app on 64-bit clients: No With this process, when I updated the installer version, I would update the version value in the detection rule, and Intune would update the installed version of 1Password when it detected a version number less than the expected value. Because the detection script provided for the MSIX deployment—AppDetectScript.ps1—does not include a version check, updating the installer version has no effect on devices where 1Password is already installed. Intune will report that the latest version is installed, but that is only because it is finding 1Password, not because it is finding the latest version of 1Password. I modified the script to include a version check, in hopes that that Intune would then behave as it had with the MSI installer, installing the latest version of the app when it detected that the installed version did not match the target version. # Modify the $targetVersion to ensure app updates $targetVersion = "8.12.10" $targetVersion = [Version] $targetVersion.ToString() # The unique 1Password identifier in detection scripts. $targetPackageFamilyName = "Agilebits.1Password_amwd9z03whsfe" try { # Per-user install (eg. Install behavior in Intune is User). $package = Get-AppxPackage | Where-Object { $_.PackageFamilyName -eq $targetPackageFamilyName } if ($package) { $ver = [Version] $package.Version.ToString() Write-Host "1Password is installed." if ($ver -ge $targetVersion) { Write-Host "1Password is up to date." exit 0 } else { Write-Host "1Password requires an update." exit 1 } } else { Write-Host "A 1Password installation wasn't found." exit 1 } } catch { Write-Host "An error occurred when detecting a 1Password installation: $_" exit 1 } As far as I can tell, the detection script worked, in the sense that it started registering the app as not installed—"The application was not detected after installation completed successfully"—but it did not cause the installed version to be updated. I know that the https://support.1password.com/deploy-1password/?windows#step-1-plan-your-deployment-windows states: To allow your team members to update 1Password, deploy the MSIX as a Win32 app and set the install behavior to User. To manage and deploy updates to 1Password, deploy the MSIX as a line-of-business app and set the install behavior to User. But all of our other Intune app deployments are Win32 apps, and, https://learn.microsoft.com/en-us/intune/intune-service/apps/apps-win32-troubleshoot#:~:text=If%20you%20mix%20the%20installation%20of%20Win32%20apps%20and%20line%2Dof%2Dbusiness%20(LOB)%20apps%20during%20Windows%20Autopilot%20enrollment%2C%20the%20app%20installation%20might%20fail., Win32 and LOB apps do not mix well when using Windows Autopilot (which we do): If you mix the installation of Win32 apps and line-of-business (LOB) apps during Windows Autopilot enrollment, the app installation might fail. I was hoping it might just work. Since it seems as though that is not the case, I was wondering if there is a technical reason why the MSIX deployment does not work as the MSI deployment did, if there is a chance that modifying the detection script in some way could work, and, given the answers to the first two questions, if there is some way this setup might be made to work in the future?
SSH Private Key sharing bug
When creating a share link for an SSH key this is what I see as the recipient. if I click copy, I get nothing moved to the clipboard, I have to select reveal, tripple click the start of the key which highlights all of it including the part I can't see, and then I can paste it somewhere. I tested on windows 11, Chrome, Firefox, and Brave Copying the public key or the fingerprint work fine. It would be nice to be able to optionally "export" the key the same way the 1pass application can, but I would settle for the copy button working.1Password Personal and Work Edge browser
Hello, I’m a Level 2 Helpdesk Engineer, and I’m currently assisting a client who uses a personal 1Password subscription for both personal and business purposes. The issue is that the 1Password extension isn’t working in his Work profile in Microsoft Edge (the one with the briefcase icon). The extension is unable to communicate with the 1Password desktop app, so it never unlocks. Interestingly, this works fine in Chrome — the extension stays unlocked and communicates with the app without any issues. So far, the only troubleshooting I’ve done is ensuring that both browsers are added/allowed in the 1Password app. I haven’t tried any additional steps yet. TLDR; 1Password Personal and Work Edge (business account) can't talk. Chrome can, and they're both added to the 1password browser list. Win11 25h2 1Pass Latest 1PassExt Latest
Managed Browser Extension
Hey all, New to 1Password for Business, long time 1Password personal user. I've just kicked off migration of legacy password manager (on-prem) for about 500 users in a Microsoft Intune full cloud environment. Our org has strict management over our Windows 11 devices... (you know, any HR opportunity to educate staff starts with I.T doing all the work with tech removing any need to teach users how to do something) I need to manage the browser extension, the usual default save vault location and watchtower etc. i thought i was on a winner with MDM ADMX - https://support.1password.com/mobile-device-management/?windows#appendix-set-the-default-vault-for-saving-new-items but this looks to be the full app rather that anything for the extension? How can i directly manage the extension via Intune?
