Seafile Server 8.0.3 SSO (shibboleth) not working

Seafile Server
1

Shibboleth SSO integration stopped working after a upgrade from 7.1.5 to 8.0.3.

When I use the [Single Sign-On] link the first time I get redirected to the shibboleth mask. I can also tell from the shibboleth logs that this step is successful.
Instead of logging me in my seafile account I end up back on the login page. Further clicking on [Single Sign-On] simply reloads the page.

I’d love to provide more detailed logs, but unfortunately there are none (except apache access logs and shibboleth). I tried to enable more verbose information as described in: manual seafile com/deploy/shibboleth_config_v6.3/
But unfortunately there is no change in verbosity.

Anyone else using 8.0.3 with shibboleth? Is there a way to get more debug information on what is going on during the auth process?

1 Like
2

+1
Also don’t know how to debug.

3

This still is borken in 8.0.5.
There is a fix in the Professinal version:

[fix] Fix SAML2 authentication

manual. seafile. com/changelog/changelog-for-seafile-professional-server/
Is this bug still in the community version?

4

In seahub_settings.py, i have renamed:
EXTRA_MIDDLEWARE_CLASSES => EXTRA_MIDDLEWARE
I believe it is because of the upgrade of Django 2.2.20…

5

Yes, you are right.

Support for old-style middleware using settings.MIDDLEWARE_CLASSES is removed since django 2.0.

We will update Shibboleth related setting in Shibboleth Authentication for Seafile v6.2 - Seafile admin manual