Envato is an Alexa top 500 website that asks you to use the same login on many different domains. The login forms are on those domains, not envato.com.
For my use case, account-level domain equivalence rules don’t work because I want to share this with a team, and multiple URLs per login is duplicative because we have multiple Envato logins.
Organization-level domain equivalence rules would be excellent, but, I think, a much bigger ask.
Envato’s equivalent domains:
tutsplus.com is another Envato domain that accepts Envato logins, but I believe it also accepts tutsplus.com-specific logins, making it not fully equivalent.
(Please excuse the lack of links, my account doesn’t have permission to post more than two.)
I’m new to Bitwarden myself, but I think the easiest way to accomplish this would be for you to modify this file: https://github.com/bitwarden/server/blob/master/src/Core/Utilities/StaticStore.cs and submit a PR back to the project. Then when they merge it, everyone benefits and not just your organization.
(Or if you run your own instance, you can always deploy that type of change locally too)
Thanks for the reply. I actually had found that file too, but the repo asks that feature requests go in the forums first, and since the global list is slim I thought they might want to be minimal about it, according to whatever criteria, and treat additions as feature requests.
I’ll make a PR if this dead ends, or the team wants me to.
FWIW I submitted a PR for something similar recently on two domains and it was accepted. However I did notice that there are lot of PRs that are just sitting around doing similar stuff. So YMMV.