Default forgot password does not work and input validation prevents one for emby from being added

[liamlows]

Description

So there are two issues noted below.

First, the default password reset functionality for an Emby setup (have not tested others) does not work. When clicking the "reset password" button, the page just refreshes and tacks on #!/startup/forgotpassword.html to the end of the Jellyseerr URL.

I believe the error resides where the baseURL is being fetched since its trying to access what seems to be a nonexistent attribute jellyfinExternalHost from the settings hook. I checked this against the settings API route and I do not see that attribute being returned nor is it listed in the default settings object.

Second, when trying to correct this by providing the proper password reset URL in the media server settings (input field "Forgot Password URL"), validation fails saying the hashbang or specifically the ! part of the hashbang is invalid. An example would be [EMBY_HOST]/web/index.html#!/startup/forgotpassword.html. The validation occurs here.

I am happy to provide a fix for this adding the necessary attribute to the settings request response pulling it from config/settings and to also updating the input validation to support hashbangs, but I figured making an issue for it first to check that is the intended functionality would be best.

Version

2.3.0

Steps to Reproduce

Issue 1:

1. Setup Jellyseerr with emby media server connection
2. After setup, logout and attempt to click "Forgot Password?"
3. Verify URL change and that navigation to Emby server did not occur

Issue 2:

1. Attempt to paste in the default Emby password reset URL in the "Forgot Password URL" input field in the settings [EMBY_HOST]/web/index.html#!/startup/forgotpassword.html
2. Verify input validation fails on the hashbang portion of the URL

Screenshots

No response

Logs

N/A

Platform

desktop

Database

SQLite (default)

Device

iPhone, PC, Macbook, any device

Operating System

Windows 11 Pro

Browser

Firefox and Chrome

Additional Context

No response

Code of Conduct

• I agree to follow Jellyseerr's Code of Conduct

[gauthier-th]

This should be fixed in develop. Can you please check?