Add secondary away from home authentication option

[syplex]

I would like others in my house to be able to login to Channels DVR while traveling and away from home, without exposing the primary account login details.

I would like to associate a secondary account to use with my DVR that can be used for remote authorization. Ideally this would be just another username/password that can be enabled by the primary account. This secondary account wouldn't have access to anything except the DVR (no payment info, no ability to post on forum, etc.)

I need an easier way for family to use channels while traveling. While traveling, they use one-off devices like computers, Apple TVs, random tablet, etc. that are usually at the location they travel to (relative's house, airbnb, etc). So I can't setup tailscale or anything fancy and just want a way for them to get it working quickly, without involving me and the primary password.

I don't need any big changes to CHDVR like multi-user capabilities etc. Just another auth!

Thanks for making such a great product that everyone wants to use so much that we have these kinds of issues!

[Fofer]

Related thread, with developer feedback and some “workarounds:”

Admin vs Viewer login

That's not true, server side settings can be applied to remote clients as well. That is true, but once they are connected, they would be bound by whatever server-side settings you configure for them. So your buddy could have access to your Channels DVR, but his remote client would only be able to view live and saved content, and not be able to delete stuff, for example. I hope he recovers well, by the way!

Also something to keep in mind:

Authorized clients and removal

It would be nice if the web interface listed the authorized web clients and had the ability to remove access for a specific client. I view this both as a security and partially a family friendly feature. There may be remote/external devices I’ve previously authorized which I no longer want to have access. Allowing all devices that have ever been authorized to remotely access the web interface/recordings doesn’t sound the most secure. Also, less important, would be a a log of section detailin…

[syplex]

Thanks for the links! I can live with the forever auth (and it looks like it will be addressed at some point), but good to know. And there are workarounds that I’m now aware of.