symfonium has been mentioned in this post before specifically for android auto. i had the same hang up with apple car play. i didn't use most of the plexamp fancy features. i just wanted it to play music and be easy to use when driving. manet finally came along for ios. though i'm still hoping one of the open source apps adds the functionality later.

the ldap auth works great for the apps. apps dont play well with an oidc login process. i ended up using both, oidc for web and ldap fall back for applications. made it easier for my non tech inclined users. most of the current apps also support quick connect, like the plex link process. you auth on a web browser and enter a code into the app. so it's possible to use only oidc for log in and, i believe it should be possible use css to even hide the user name and password fields.

honestly every explanation probably just ends at 'this is what i learned on and it works'. same way i religiously use nano and try to do everything in bash first. or how a couple coworkers can't stop explaining their vim workflow and defending python unprompted like it's a trauma response for them. my current homelab is also running a r9 with 64gb ram and 30tb storage. if i were paying for remote hosting, still using salvaged hardware or being paid, i'd invest time learning newer processes. but containers haven't caught my interested and this set up takes basically no effort on my part to maintain, so i can focus my limited free time elsewhere.

https://github.com/jellyfin/Swiftfin i've got 5 apple tv users, two android tv and one webostv

if you use the oidc connection and apps that support quick connect you can do it. you basically end up doing things like the plex link process that got implemented when they forced everyone into their authentication service. i almost went that route but opted to leave the password auth from ldap in. its the kind of log in process most people are used too and i've got a few elderly users. i disabled password reset in authentik though and everyone gets a 3 word 24 char minimum password.

https://github.com/jellyfin/Swiftfin

i ended up doing both. ldap for the apps. oidc for web based users and the apps that support the quick connect feature. the local user account system works fine too, and ldap would be enough. i just wanted an excuse to play round with sso systems, and it was fun figuring out how to connect all my servers.

authenik has a good docs site for both it's docker container and connecting it to jellyfin. Authelia looked interesting too.

it's just what i'm comfortable with. started playing with linux servers before docker existed. i've got frigate and authentik running in docker, but if i have the option to run something outside docker i still prefer that.

https://github.com/intro-skipper/intro-skipper
*edit it's such a common complain this got posted twice at the same time :)

plex is still definitely easier to get started on. i don't begrudge anyone still going that route, i had a lifetime plexpass the last 8yrs i think. jellyfin is a great option if you either already know how to set things up and want full control. Or you're looking for an opportunity to learn more about reverse proxy, dns and authentication/access systems. plex is still i nice gateway drug.

authentik is an identity server. theres a couple free ones available, this one just worked for me. it provides oauth and ldap fallback for the jellyfin server. along with login for most of the other servers i host like nextcloud/calibre-web/lychee etc. it has a nice easy log in process along with a 'homepage' kinda thing for everything my users can access with their account. makes it easier to support the non technical friends and family.

yeah it took me about 6 months with jellyfin to feel like i was ready to finally kill plex. the thing that finally did it was getting an email from plex asking if i'd like to check out whats streaming on hbomax.