web interface - access control?
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
web interface - access control?
for the very nice web interface (is it new in 4.0?) - is there some form of access control planned? I would like to have something like subsonic has for it's mp3 server..
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: web interface - access control?
It has a built in access control already. First you must enable it. This is done by setting
Then you must add users. Simplest way to do that is to use the GUI and go in to the "Plugin" tab.
At the bottom you'll have a credential section were you either via the GUI can add lines or you can open the raw file.
To the file (or add one entry at the time using the GUI) add lines of format:
where the is optional.
The tag can be whatever but view it as a group. All users with the same tag will be treated the same. If no tag is supplied the user is considered to belong to the group of himself.
Groups can then be used to differentiate rootfolders etc.
Once your done with all this you probably need to restart UMS and the off you go.
in your UMS.conf (no GUI option here).web_authenticate=true
Then you must add users. Simplest way to do that is to use the GUI and go in to the "Plugin" tab.
At the bottom you'll have a credential section were you either via the GUI can add lines or you can open the raw file.
To the file (or add one entry at the time using the GUI) add lines of format:
Code: Select all
web.<tag>=usr,pwd
Code: Select all
.<tag>
The tag can be whatever but view it as a group. All users with the same tag will be treated the same. If no tag is supplied the user is considered to belong to the group of himself.
Groups can then be used to differentiate rootfolders etc.
Once your done with all this you probably need to restart UMS and the off you go.
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: web interface - access control?
Nice to have all these hidden options defined in UMS.conf, like many renderer options are already defined in PS3.conf 

- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: web interface - access control?
Well GUI and documenting isn't my strong/best side. I documented here right?ExSport wrote:Nice to have all these hidden options defined in UMS.conf, like many renderer options are already defined in PS3.conf

The web would benefit from a complete tab in the GUI (with it's options) but thats on the todo list. I wanted the function out the door. And then add more functions that needs more config which isn't documented either

We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: web interface - access control?
Totally understand
Only wanted to say we have so many cool hidden settings but no one know about them and it is impossible to find all of them here in the forum and maintaining them on one place
Keep up great work.
ExSport

Only wanted to say we have so many cool hidden settings but no one know about them and it is impossible to find all of them here in the forum and maintaining them on one place

Keep up great work.
ExSport
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: web interface - access control?
One way to find out about new cool config options is to look in this file https://github.com/UniversalMediaServer ... ation.java
All constants at the start of the file shows you which keywords can be put into the UMS.conf
(....KEY_ALTERNATE_SUBTITLES_FOLDER = "alternate_subtitles_folder") the keyword is whats between the "
what the value should be can sometimes be deduced from the name (web_enable,max_bitrate) or by searching for that uppercase crap in that file.
All are used in a function returning one out of String,int,boolean.
The new undocumented stuff added by me are mostly just boolean or int options.
You don't need to be a java wizard (or even a programmer) to make a good guess of what to put there. For boolean options it's simply on(=true) or off(=false).
All constants at the start of the file shows you which keywords can be put into the UMS.conf
(....KEY_ALTERNATE_SUBTITLES_FOLDER = "alternate_subtitles_folder") the keyword is whats between the "
what the value should be can sometimes be deduced from the name (web_enable,max_bitrate) or by searching for that uppercase crap in that file.
All are used in a function returning one out of String,int,boolean.
The new undocumented stuff added by me are mostly just boolean or int options.
You don't need to be a java wizard (or even a programmer) to make a good guess of what to put there. For boolean options it's simply on(=true) or off(=false).
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: web interface - access control?
Yes I know where to look at
I already did the same for hidden renderer config options and pulled the change officially.
Problem is another. You need to read many code around what exactly the hidden settings does and in most cases it is quite hard work to imagine what which settings probably should do
It is time consuming and requires some programming skills
Not problem for me but can be impossible for others. When I will have more time I wil try sum them up, but the time, free time.... 

Problem is another. You need to read many code around what exactly the hidden settings does and in most cases it is quite hard work to imagine what which settings probably should do

It is time consuming and requires some programming skills


Re: web interface - access control?
Hello!
i don´t understand the (complicate) procedure:
what means in (Plugins) the Owner & Tag ?
i only want to authenticate the webserver with an user and password - not more - not less.
e.g. i want to login: alex and PW: test
what is to enter to work it right ?
confusing: if i set in in the config file the "web_authenticate =true" than he promts me on the browser for a user and a password - but i have it never set
Thank you for your help!
i don´t understand the (complicate) procedure:
what means in (Plugins) the Owner & Tag ?
i only want to authenticate the webserver with an user and password - not more - not less.
e.g. i want to login: alex and PW: test
what is to enter to work it right ?
confusing: if i set in in the config file the "web_authenticate =true" than he promts me on the browser for a user and a password - but i have it never set

Thank you for your help!