Manual?
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
Re: Manual?
There is no manual that I'm aware of, but there are some (mostly outdated) documentation that comes with UMS. Some documentation can also be found in UMS' GitHub Wiki. That said, what you're asking for is how to use the renderers (Kodi, VLC), not UMS. UMS should already be available to Kodi, VLC and any other UPnP/DLNA capable renderer when it's running, so you need to check the renderer software's documentation for how to use them to navigate a media server.
There is no security in the UPnP AV/DLNA protocol specification. It was never intended to be "secure", it doesn't even have any form for authentication. That said, there does exist some things you can do, like IP filter in UMS or enabling the use of a code to be able to enter certain folders. I'm not sure how well these features work though.
Security should normally be a concern though (I guess it depends on what you mean with "security"). UMS is read-only, so there's no way a renderer/client can modify or delete content on the server. If you mean, access control with "security" the above applies. It should be mentioned though that UPnP relies on multicast, which isn't routed on the internet, so it is "secure by design" in that sense. If you want to prevent others on your local network from accessing the content, you're basically out of luck except the above.
There is no security in the UPnP AV/DLNA protocol specification. It was never intended to be "secure", it doesn't even have any form for authentication. That said, there does exist some things you can do, like IP filter in UMS or enabling the use of a code to be able to enter certain folders. I'm not sure how well these features work though.
Security should normally be a concern though (I guess it depends on what you mean with "security"). UMS is read-only, so there's no way a renderer/client can modify or delete content on the server. If you mean, access control with "security" the above applies. It should be mentioned though that UPnP relies on multicast, which isn't routed on the internet, so it is "secure by design" in that sense. If you want to prevent others on your local network from accessing the content, you're basically out of luck except the above.
Re: Manual?
I don't think .htaccess will do anything for you here, as UMS use its own HTTP server implementation that does just what's needed for UPnP AV to function, so things like that aren't implemented. If you're thinking of web-interface access, it is possible to enable HTTP basic authentication - but this doesn't apply to renderer access via UPnP.