I recently decided to dive a bit deeper into flows since the plugin stacks were failing on me sometimes. Cobbled together something from the examples provided, seems to work fine for me now. Depending the worker it runs on it tries to transcode with nvenc or qsv, if it fails or is not available the flow falls back to cpu transcode.

deleted by creator

If qBittorrent is not complaining about file errors you are in fact still seeding the original file. Especially on Linux file systems a file keeps being referenced as long as at least one application is still accessing it, regardless if you delete, rename or alter it. Once you close qBittorrent the ‘old’ file will be dropped though.

And at that point it won’t be seeded anymore as it does not match the checksums that are stored in the .torrent file or were retrieved via a magnet link. If the client is not broken it should not be possible to seed corrupted or altered files.

After looking deeper into the docs they do not support and do not plan to support the Relying Party role. So it probably won’t fit for this use case.

Depending on what you are trying to do, Authelia does have OIDC in beta https://www.authelia.com/roadmap/active/openid-connect/

I use Authelia again since in beta it now supports multiple Pass/FIDO keys via the web interface, and it does work reasonably well.

Well, how about having a local API and have no calls at all to your cloud infrastructure? Probably too easy and you cannot lock people into your ecosystem.