SSO: Not yet planned
LDAP: Development COMPLETED - BETA AVAILABLE
>180 direct endorsements
>30 MONTHS (>2.5 years)
PLEASE BUMP - - - - - PLEASE LIKE - - - - - PLEASE BUMP - - - - - PLEASE LIKE - - - - - PLEASE BUMP
This would greatly expand Emby's usage, and possibly more enterprise level adoption, user templating, user groups, SSO, etc. There are also users who have completely abandoned Emby and ended subscriptions due to the lack of this necessary basic functionality.
Note: SAML2 is also part of this request. (header auth is also acceptable, at a minimum.)
Context: I am trying to use something like openfire as a Instant Messaging solution which already supports LDAP and SAML2. So this would allow the current user of emby to seamlessly use web-based instant messenger with the same username and password as Emby without the need to enter them into a form. This would also allow universal login to be shared with my home PC's, Spiceworks, Ombii, Organizr, etc. The multitude of possible flexible functionality this could add is truly incredible. THIS NEEDS TO BE DONE, myself and others cannot manage a userbase with proprietary passwords for a single service (with no self-service password reset/recovery), when things that have only months of development implement it within days, easily.
- LDAP - Development Completed - BETA AVAILABLE!
- SSL is NOT actually needed, but Emby team insisted on it anyways:
- Simply offering a toggle option for auth to send plaintext or encrypted passwords would work just fine.
- It is ironic to claim the need to be overly security conscious of user passwords, while lagging behind on basic SSL.
- If SAML is implemented, a SAML request/response can just be signed by an x509 and it is just as secure as TLS using SSL.
- SSL does not need to be natively supported, as it is perfectly possible to run it through an SSL reverse proxy tunnel and have the same effect.
- SSL Feature Request: https://emby.media/c...rt/#entry322526
- As of now username and password is encrypted client-side as security as SSL is not natively implemented.
- Emby team has said this impedes the adoption of both SSO and LDAP.
- Please see our SSL request topic; like, comment, and endorse it to show how many people would enjoy/gain from this basic security.
Ways to satisfy this FR:
- Direct LDAP connector
- SAML2 connector
- General SSO functionality (SSO Header, etc)
- Allowing user header auth
- NGINX auth support
- RADIUS Authentication
Other features that are inherently possible if this is implemented:
- Self service passwords
- Ability for users to invite users/guests
- Expiring Accounts (after duration/trigger)
- Unified credentials for many services
- Corporate level authentication security
- User groups
- Mass User management
Update 1: I encourage others to work on this but I am currently seeing what I can do to develop a solution to this myself. If you have experience in this LDAP/SSO/SAML2/SSL/.NET contact myself, @Luke, @ebr or the Emby team to let them know, any help is greatly appreciated! By everyone!
Update 2: I know there is always the question of "well how many users actually want/will use this", so I compiled a list of some of the other threads/sites where people request this (to apparently no effectiveness in motivating the team).
Update 3 (18 MONTH UPDATE): This request has now hit 18 months in age, NO progress made thus far whatsoever. ( )
Update 4: This FR is now the 4th most liked post ON THE ENTIRE FORUM and the 3rd most liked FR ON THE ENTIRE FORUM (ever), the 1st most liked active FR ON THE ENTIRE FORUM and over 4000 views. Counting endorsements besides those on this thread show over 115 direct requests/endorsements for this basic functionality. Lets get this moving guys, this is getting to be a bit much. Almost 2 years waiting on this now.
Update 5 (9/20/2017): This feature request is now the MOST DESIRED REQUEST EVER MADE TO EMBY, sadly, that has not merited any progress at all. The staff has been working on things they believe Emby users want or may want, but it is clear what people want. We can only hope now our wishes are respected instead of being told what we want and having our requests dismissed.
Update 6 [2 year update] (10/17/2017): Two years and not a single bit of progress has been made. TWO YEARS!!! To say this is disappointing is an understatement. The entire reason I went from Plex to Emby was because of local user management. THIS IS THE ONLY REASON, so naturally I wanted to have complete control over my users, but after TWO YEARS, still nothing.
Update 7 (3/6/2018): DEVELOPMENT HAS STARTED!!! Check Luke's recent comments, if you want to test it out, download the latest beta and install/configure the LDAP plugin to test and give feedback!!!
Update 8 (4/6/2018): Development on the LDAP connector has completed from what I gather, not sure if this is only a beta or a primary release; SSO is still a plan for the future but has not been touched.
Progress made by other users (looks to be nearly, if not fully complete):
Exploits shown by other users against Emby (emphasizing the need for a centralized authentication solution):
Related FR that could be helpful:
Any of these could be interesting to have compatibility with:
LDAP/SSO/SAML Requests (~180 endorsements) [>12,000 views]
- > 95 endorsements on this post
- ~ 30 endorsements
- > 35 endorsements
- > 14 endorsements
- > 4 endorsements
- Interview, in article comments user said lack of LDAP STOPPED him from using Emby (Emby is actually losing customers due to the lack of this NECESSARY basic functionality):
- Duplicate, user had no progress on first 2 posts (no one from Emby actually tracked this or even replied to him):
- Auth announcement, user 'Drashna' in comments requested LDAP/AD
- Various similar requests
- External SQL auth request:
#ADFS #SSO #LDAP #ActiveDirectory #MSAD #SAML #SAML2.0 #SAML1.1 #PingFederate #OKTA #LemonLDAP #JASIG #authentication #auth #TLS #SSL #Usergroup #usertemplate #header #authheader #headerauth #security #hardening #authhardening #authenticationheader #externalauth #centralauth #centralizedauth #centralizeddb #exploit #authexploit #security #loginhardening #authenticationhardening #accesscontrol #.NET #SelfService #RADIUS
Edited by Untoten, 06 April 2018 - 09:20 PM.