Add Federal Identity Providers to Sign In
I’m a disabled veteran, and I use one of the secure sign-in systems accepted by the U.S. Department of Veterans Affairs (VA) to reach my benefits and services. The VA now directs veterans to ID.me or Login.gov after removing DS Logon on November 18, 2025. 1Password recognizes neither provider inside its “Sign in with” field.
The Defense Health Agency is replacing DS Logon with myAuth across TRICARE-related platforms by the end of fiscal year 2026. milConnect and ID Card Office Online have already switched. myAuth now belongs beside ID.me and Login.gov as a first-class provider.
I’ve got several government-service Login items whose authentication belongs to one of these providers. 1Password forces me to approximate that relationship through Related Items, tags, or notes. The workaround hides the identity provider that actually controls access.
1Password should add first-class “Sign in with” support for ID.me, Login.gov, and myAuth. A user-defined provider field would solve the larger problem across military, veteran, federal, regional, and enterprise accounts. The ability to save and edit provider relationships and receive reminders — similar to 1Password’s current Okta treatment — would still carry real value before browser automation arrives.
The existing ID.me request (PB-40987004) and Login.gov request (PB-51271482) already document demand; myAuth and a user-defined provider model now give 1Password a broader solution.
The supporting links: