My company uses Office 365 logins for a number of things, including our VPN and SSO to certain services. For some services I need to use my full email address as my login, but for other services I need to omit the domain, so I've found my choices are either to have near-duplicate entries in 1Password (and ignore the warnings that I've reused the password), or to have only one entry and manually delete the domain from the ID field for the services that require I not use it. I'm hoping that there is - or could be! - a better way. This is probably better explained with a few examples:
Let's say our domain is foo.com and my Office 365 ID is [email protected]. To login to our VPN I use [email protected] with my password. I also have a Google Auth-type one-time password stored in 1Password. So far, life is good.
But we also use a self-hosted instance of the application bar.com. Normally people would login at bar.com with their full login (e.g. [email protected]) but because we host our own instance, I need to login at foo.bar.com with only the username joel, as @ foo.com is assumed. But despite the two different usernames, my VPN and this service are authenticating [email protected] at Office 365. Further complicating the matter, foo.bar.com also supports OTP but it's implemented in that service, so it's a different OTP. As a result, here's what this login looks like in 1Password (domain name of main username field, websites, and name of secondary service redacted. Enjoy the expired OTPs though!)
What I guess I'm hoping for is either a way to link multiple logins to the same password (in a way that recognizes this is safe, and not me being dumb and sharing passwords), or a way to specify within a single login that the username field might take multiple formats - with or without domain name. The latter approach would still require me to deal with OTP manually though, as I do today.
So if this already exists, any education on how to do it would be greatly appreciated. If not, I assume I'm not the only one dealing with SSO-related username issues like this, so please take this as a feature request. If I haven't explained the issue clearly above, my apologies, and please feel free to request clarification.
1Password Version: 7.3.2
Extension Version: 126.96.36.199
OS Version: macOS 10.14.6
Sync Type: iCloud