econ 74 Posted February 5, 2016 Share Posted February 5, 2016 Within Emby I limit the devices my users can access from. Ex. I have a user who I only have their Roku devices checked within the Device Access page within their user access page (enable access from all devices is also unchecked). When recently reviewing my recent activity on the server I noticed that this particular user was able to access via Chrome. Am I missing a setting or possibly what Device Access is meant to be used for? I am looking to only let a single user access from the devices checked. Link to comment Share on other sites More sharing options...
Luke 37057 Posted February 5, 2016 Share Posted February 5, 2016 That doesn't include browsers (as explained lower below). the fact that browsers are showing up in that list was probably just a temporary defect that has since been corrected. Link to comment Share on other sites More sharing options...
econ 74 Posted February 5, 2016 Author Share Posted February 5, 2016 Ahhh, missed that part. Any reason as to why we wouldn't deny the browsers access? Technical limitation currently? Thoughts to include it in the future? Link to comment Share on other sites More sharing options...
Luke 37057 Posted February 5, 2016 Share Posted February 5, 2016 no real plans because they can't be permanently uniquely identified. Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 5, 2016 Share Posted February 5, 2016 no real plans because they can't be permanently uniquely identified. Unfortunately, that is true. Link to comment Share on other sites More sharing options...
econ 74 Posted February 5, 2016 Author Share Posted February 5, 2016 Instead of attempting to uniquely block individual items couldn't it be written to block all except what is checked? Link to comment Share on other sites More sharing options...
carlbme 13 Posted February 6, 2016 Share Posted February 6, 2016 (edited) Would it be possible to change the listening ports? So that way anytime someone does try to connect using the browser it'd fail to establish the connection. My only thing is I'm not sure how that would affect the apps. Edited February 6, 2016 by carlbme Link to comment Share on other sites More sharing options...
Luke 37057 Posted February 6, 2016 Share Posted February 6, 2016 Would it be possible to change the listening ports? So that way anytime someone does try to connect using the browser it'd fail to establish the connection. My only thing is I'm not sure how that would affect the apps. The ports are configurable in the server dashboard. it would temporarily hinder apps because they do save connection information. this can be corrected when the app auto-discovers the server, or via manual address entry. Link to comment Share on other sites More sharing options...
blakeusblade 3 Posted February 10, 2018 Share Posted February 10, 2018 I know this post is old... but I'll try my luck! Unfortunately, In order to limit a particular user to just the web interface (and not allow on devices). One must enable access from all devices in order to allow this. It would be good to have a generic item in devices that represents web browsers generically. This would allow control over the web browser interface! Limiting users to just the webpage.... For example, I have a user who I want to just have permission to download the raw file. At present I need to enable there access from all devices else they can't access the web page. I don't want them to use or have permission to use any emby app or device except the web interface. Having a generic device that represents the web interface would allow control... Link to comment Share on other sites More sharing options...
Luke 37057 Posted February 10, 2018 Share Posted February 10, 2018 Yes that could be possible, thanks. Link to comment Share on other sites More sharing options...
blakeusblade 3 Posted March 10, 2018 Share Posted March 10, 2018 A mentioned workaround... https://emby.media/community/index.php?/topic/49931-add-web-browser-to-device-access-list/ Posted 19 February 2018 - 08:49 PM To workaround the issue.... Simply install EMBY on a device... connect it to your server... NOTE the device appearing in the dashboard... Rename/relabel device to WebUI... Uninstall EMBY app from device... Assign users you want WebUI access only to the device just added... Remove users from all devices except the device just added... BOOM! Done... While this does use up a device license, it does get around the issue... Its worth noting... That users only need to be granted access to only 1 device to access the WebUI/Webpage... By giving them access ONLY an EMBY device thats been uninstalled and nothing else, your only granting them access to the WebUI/Webpage and nothing else... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now