Users
Existing users
You need a user account for logging into the web interface of MyTunesRSS. You can create any number of user accounts. The page displays the names of all users on the left side. Right-click in the empty space for a popup menu with the option to create a new user. Right-click on an existing user for a popup menu with the options to delete the user or create a child user. A child user inherits most settings from the parent user. Only a few things can be configured individually for child users. Use this to have a common set of options for a number of users with the ability to change these common options for all users with a single click.
When creating or editing a user you will see the options of the user on the right side of the dialog.
Identification
You have to assign a unique user name and a password for the user. The password is not displayed. You can also assign an email address which is necessary if the user forgot his password and wants to create a new one.
Permissions
You can select permissions for each user. So you can have a user which is allowed to use the Flash player only for example and will not be able to download anything or you can remove the permission for uploads for example. A user can further deselect some of the options later in the web interface but he cannot get more permissions than you select here. If you give the user the permission for transcoding, the user must activate transcoding in the web interface settings as well. The permission just grants the user the right to use transcoding, it does not automatically activate it.
Options
In the web interface search you can either use the standard search which finds things matching your query terms exactly as well as similar spelled stuff or use a search which only finds exact matches. If you configure a search fuzziness for a user here, only this value will be used and the user will not have the select box with the above mentioned options. A search fuzziness of 0 only finds exact matches while 100 (the maximum value) returns nearly anything no matter what your search terms have been.
The download limit can be set per day, week or month. You have to enter a value for the limit size and select if this limit is per day, week or month.
You can also set a maximum count of files per archive, so a user cannot download really big files. A limit of 15 for example will be sufficient to allow downloading most albums but will prevent users from downloading everything from one artist in a single archive for example.
The session timeout defines how long a user can be inactive in the web interface before being logged off automatically.
The bandwidth limit can be used to restrict user sessions to a certain bandwidth. This setting applies to streaming content.
The user can be limited to the tracks of certain playlists. You can create a playlist per user for example and limit the user to the tracks of this playlist. You might also have a special public playlist which is used for all users in MyTunesRSS. This way you can prevent users from seeing all your tracks. This applies to album, artist, genre and playlists as well. Since the tracks count per album, artist, genre and playlist is calculated once during the database update, the counts in the web interface always show the total number of tracks and not the limited ones. This means the user might see an artist with 100 tracks but gets 10 tracks only when selecting the artist if he is limited to a playlist with only 10 of the 100 tracks of that artist. Albums, artists, genres and playlists with no tracks because of the limitation are correctly hidden from the user. This issue might be resolved in later versions of MyTunesRSS.
If you check the option to store web settings in the user profile, all settings made in the web interface are stored in the user. Without this option the settings are stored in a browser cookie only. Use this option if you work without cookies or to setup defaults for users without cookies. In the latter case, check the option, log into the web interface with the user you want to create defaults for, edit and save the web settings and then uncheck the option again. Now you have settings stored in the user profile which won't get overridden anymore when changing settings in the web interface. The settings from the web interface are stored in the browser cookie only which overrides the (default) settings from the user profile.
If you enter Last.FM account information for a user, information about played tracks is sent to Last.FM.
Links in the web interface are encrypted by default, so if you have one link, you cannot guess any other links from it. You can for example give a link to an RSS feed to someone else and he can use the feed. But he cannot guess any other links and get more access with it. You can optionally switch off this encryption. The links are a little shorter in that case and you can guess other links and get access to other content.
Information
The right part of the window displays information about the user. It shows how much the user has downloaded since the last reset with the button below this information. There will also be information on the download limit of the user if you have setup one. You can see how much the user has downloaded and how much he can still download.
LDAP configuration
You can use an LDAP server for authentication. Click the "edit LDAP" button to setup your LDAP server connection. For more information on LDAP please refer the other sources on the internet.
You have to configure your LDAP server host and port as well as the authentication method. Currently only SIMPLE is supported. Whenever a user tries to login into the MyTunesRSS web interface, first the local users are searched for one with a matching login name and password. If no matching user is found (either no user with the name exists or the password does not match), the LDAP server is used (if configured). MyTunesRSS tries to connect to the LDAP server using the configured authentication principal. The princial supports a placeholder {0} where the login name specified in the login form is inserted. The password is used from the login form as well. If the login is successful, a user with the same name is searched in MyTunesRSS. If it exists, the user is logged in, i.e. the authentication was done using LDAP and now the corresponding local MyTunesRSS user is used. If no such user exists, which is usually true for the first time an LDAP user logs in, a new one is created. MyTunesRSS fetches the configured template user and creates a copy with the name that was just authenticated using the LDAP server. So the template user configured here is the template for all LDAP users when they login for the first time. The new user does not become a child user of the template user. If the template user has a parent user, the new user will have the same parent. If you have a search root and expression configured, MyTunesRSS now searches the LDAP using this root and expression. The search expression can have the {0} placeholder for the user name as well. The attribute with the name configured in "mail attribute name" of the first result is then copied into the email of the newly created MyTunesRSS user.
So, for using LDAP you have to configure the LDAP server, an auth principal with the {0} placeholder, an optional search expression if you want to copy the email from the LDAP to the MyTunesRSS user and a template user.