Thanks for all your hard work - this project is great. The title is a little misleading but I did not know how to describe it.
I have vaultwarden set up on two domains (I know that you can only specify one). One for regular usage that blocks access to the
/admin path and one that does provide access to the admin panel but is protected by mTLS. This was also the main reason why I needed two domains for this, as you can not have different TLS configurations for the same domain (btw: the Bitwarden Apps support mTLS which is awesome). I am already using this for quite a while and it works great. However there is a minor inconvenience when logging in to the admin page. When I log in with the admin key it will correctly log you in and create the session cookie, however the page will redirect you to
https://admin which obviously is not a valid url. I can just enter the page again and I will be logged in and can use the page normally from there on.
So this is probably a very specific request and I can imagine not too important but maybe there could be a second base domain config setting that would just default to the other one if not provided.
I imagine there are more important issues as this is a not supported use case but I do not know a lot about Rust. I looked into patching it myself but I would appreciate a little guidance on where to start.
I found this: vaultwarden/admin.rs at main · dani-garcia/vaultwarden · GitHub
But I do not fully understand how the config works. Can I just add the entry here vaultwarden/config.rs at 7b742009a180c990c013df51946ab22aa02c7a96 · dani-garcia/vaultwarden · GitHub and it will be available in the admin.rs? I don’t need there to be a setting in the admin panel.
I can understand if this is just not supported and you can not help me. But I figured asking where to start does not hurt. It’s also not the end of the world since you don’t need to log in to the admin panel very often and pressing “back” once is just a bit annoying but nothing major.