Updated Issue:
Quarkus mainly offers OIDC as authentication mechanism, which also supports multi-tenancy. For Opencast we also need:
There is a middleware to translate Shibboleth to OIDC and LTI 1.3 (according to the docs) is also using OIDC so neither of them should need additional work.
JWT in Opencast is in large parts a custom implementation, so we might just adjust our custom code rather than using the Quarkus JWT Authentication Mechanism.
Digest needs to be implemented.
Multi-tenancy needs to be configured / implemented independent from the Authentication Mechanism.
Updated Issue:
Quarkus mainly offers OIDC as authentication mechanism, which also supports multi-tenancy. For Opencast we also need:
There is a middleware to translate Shibboleth to OIDC and LTI 1.3 (according to the docs) is also using OIDC so neither of them should need additional work.
JWT in Opencast is in large parts a custom implementation, so we might just adjust our custom code rather than using the Quarkus JWT Authentication Mechanism.
Digest needs to be implemented.
Multi-tenancy needs to be configured / implemented independent from the Authentication Mechanism.