We have some sites that all use some sort of central ID - example US Federal Government services like FinCEN, Passport Services, STEP etc all leverage the US government login.gov as a central store. They are still separate accounts and URLs, that redirect to login.gov for authentication and then take you back to their site. Same for United Healthcare, which uses a central auth service for Optum, UHC etc. If I save them as separate sites, they show up as risk due to using repetitive passwords. I also have to store 3-4 URLS with the same password e.g. state.gov site will redirect to login.gov site and so need both domains stored separately to allow for autofill.
Can the vault data fields allow for a redirected URL field, or some sort of logical binder that would allow the vault to know that site A, redirects to site B i.e. instead of storing username and password, we store the redirected domain? That way only 1 place for the password itself to be stored.
Hoping that made sense.
Thanks!