You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have JFA-GO set up to send password reset links to users' emails. Obviously Jellyfin can't do this though, so when a user clicks "Forgot password" on the Jellyfin sign-in page, it tries to reset it through Jellyfin (and fails if they aren't in my local network).
In my own setup, I modified the "session-login.c88fc4019dc5f2693ced.chunk.js" JavaScript file in the WebUI files
Now, whenever a user clicks "Reset password" in Jellyfin, it opens JFA-GO in a new tab on the page where they can reset their password (if the "My Account" page is turned on)
Would this be possible to automatically inject into the JS if the config directory is linked to JFA-GO? I'd imagine my manual change will break as soon as they update the WebUI in some way that changes the javascript
The text was updated successfully, but these errors were encountered:
I love the idea and I will use it in my setup. Have yet to deploy JFA go myself as I've been using Wizarr instead but only now realized that it doesn't handle password resets. Just a quick question, does it still work with Jellyfin 10.9.x ?
I have JFA-GO set up to send password reset links to users' emails. Obviously Jellyfin can't do this though, so when a user clicks "Forgot password" on the Jellyfin sign-in page, it tries to reset it through Jellyfin (and fails if they aren't in my local network).
In my own setup, I modified the "session-login.c88fc4019dc5f2693ced.chunk.js" JavaScript file in the WebUI files
I just changed the value of
to
Now, whenever a user clicks "Reset password" in Jellyfin, it opens JFA-GO in a new tab on the page where they can reset their password (if the "My Account" page is turned on)
Would this be possible to automatically inject into the JS if the config directory is linked to JFA-GO? I'd imagine my manual change will break as soon as they update the WebUI in some way that changes the javascript
The text was updated successfully, but these errors were encountered: