Error 403 and 404s after OC 10 upgrade

[Huber, Daniel]

Hi all,

I recently upgraded our Opencast installation (admin/presentation/worker, multi-tenant setup, LDAP-integration) from version 9.4 to 10.0
Afterwards I experienced some error 403s when loading required assets in the admin UI or the media module. Most notably, Paella player was not able to load at all.

After disabling the static file authentication introduced with OC10 in org.opencastproject.fsresources.StaticResourceServlet.cfg:
authentication.required = false

the error 403s disappeared but some error 404s appeared. E.g. when I try to access the video player from the admin UI, I get

HTTP ERROR 404 Not Found
URI: /play/f1291e9a-00d4-4bf2-a739-24c1a11d0e6c
STATUS: 404
MESSAGE: Not Found
SERVLET: org.ops4j.pax.web.service.spi.model.ServletModel-54
Powered by Jetty:// 9.4.28.v20200408

I guess this has something to do with the user session because if I click shift + refresh (on Firefox), Paella player loads as expected and I can play the video.
But I get a bunch of additional error 404s (paella logo, some fonts) until I do another shift + refresh (at the same time I get logged out from the admin UI still opened in the other tab)

The behavior persists no matter if I log in as a local or LDAP user. The logs show no errors or warnings other than:

2021-07-06T08:30:53,575·|·ERROR·|·(Log:186)·-·[org.osgi.service.cm.ManagedService,·org.opencastproject.kernel.mail.SmtpService,·id=210,·bundle=80/mvn:org.opencastproject/opencast-
kernel/10.0]:·Unexpected·problem·updating·configuration·org.opencastproject.kernel.mail.SmtpService

2021-07-06T08:30:49,890·|·WARN··|·(ServletContainerInitializerScanner:136)·-·failed·to·parse·and·instantiate·of·javax.servlet.ServletContainerInitializer·in·classpath

Another thing I noticed (no idea if it is related): When I try to access /api/info/me, I get java.lang.IllegalArgumentException: Value of field 'name' must not be null.

I am not quite sure why the static file authentication does not work and what causes the error 404s and have no idea how to further investigate this issue. Maybe someone can give me a hint.

Thanks,

Daniel

[Huber, Daniel]

Sorry, I forgot to add the log files:

Admin node: https://dpaste.org/61vR
Presentation node: https://dpaste.org/FNoU

(including an Opencast restart on both nodes)

Best regards,

Daniel

[Greg Logan]

Hi Daniel,

Looking through the logs I don't see any obvious issues aside from the errors you're seeing.  I'm going to guess there's some misconfiguration either in the core Opencast configs or in the security/ldap/org integration - the same error you're seeing at /info/me.json seems like it's happening in the logs as part of some of Opencast's internal health checks, and that speaks to something being very very wrong.  If you turn off LDAP and *just* have local Opencast auth does this work as expected?  Likewise, turn off the multitenancy and see if that fixes things.

As far as I know nothing we've done should have broken any of this, but obviously *something* is broken :)

G

--
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.