question about multi user support

[Splinter7914]

excited to try it out.

One thing I was not sure about if in the mapper file do I also need to add the user that is currently associated with the backends? I was thinking of adding it but was not sure if it would break something. Explicitly mentioning this in the faq could be useful.

Also I assume this means we should also update the webhooks in Jellyfin to be for all users we are adding in the mapping? Would be good to add that to the FAQ?

FAQ also mentions that there is minimal support for this. So wanted to understand what is not expected to work?

[arabcoders]

excited to try it out.

One thing I was not sure about if in the mapper file do I also need to add the user that is currently associated with the backends? I was thinking of adding it but was not sure if it would break something. Explicitly mentioning this in the faq could be useful.

Also I assume this means we should also update the webhooks in Jellyfin to be for all users we are adding in the mapping? Would be good to add that to the FAQ?

FAQ also mentions that there is minimal support for this. So wanted to understand what is not expected to work?

Sorry for late reply, for some reason, i wasn't getting any emails from GitHub. A FAQ entry about the support can be found at this link.

The multi-user support is implemented via standalone command state:sync which is right now kind of disconnected from the rest of WatchState, except in narrow case which is progress sync which is triggered via the on_progress event.

I have already implemented the foundation for expanding support in the future if need arises, however right now i am content with the available features for mutli-users setup.

However, should there be a need for more features we can implement them.

[Splinter7914]

No worries, My question on should the admin users (user the backend were setup with initially) be added to the mapped file or not is not explicitly mentioned. So I was not sure if I should be adding them or not. Or is mapped file only for all the other users?

Not asking for anything extra, was simply suggesting that in the FAQ we could add a blob stating update your Jellyfin webhook as in the webhook setup it mentioned only enable it for a specific user. So anyone adding multi user support should go back to the webhook settings and enable other users as well.

[arabcoders]

Hi, sorry i wasn't clear, the state:sync command doesn't require mapper file, it uses your main servers.yaml as starting point to inquiry about the backends users, once that is done is try to auto match them and fallback to mapper file if it fails to match them.

The main user, is auto ignored by state:sync as it's state already handled by the main system, however that can be overriding by adding --include-main-user flag to the task.

Webhook isn't effected by the multi-user currently, as it's only works for the main user. Should we implement support for it in the future, indeed we need to update the docs to mention that we need all users to have their own webhook endpoint limited to their user =)

Thank you for your suggestion

[Splinter7914]

Thanks, I will try it out. Curious how does auto mapping work? Does it look for same name? My uses have different names so they will fall back. I was just curious is all.

[arabcoders]

Thanks, I will try it out. Curious how does auto mapping work? Does it look for same name? My uses have different names so they will fall back. I was just curious is all.

Indeed the matcher uses their username as it's the only thing available to compare. And in your case yeah i think you going to need a mapper file to link up users