Shibboleth login redirects to login page upon successful authentication

I’ve been trying to implement shibboleth login to my Seafile server. Everything seems to be working normally except for the fact that upon successful login on the IdP page, I’m redirected back to the regular login page instead of the users home library. All I can find in the logs is:

DEBUG Shibboleth.SSO.SAML2 [23]: ACS returning via redirect to: https://cloud.fsmse.de/shib-login/?next=/

What could be causing this and how do I best go about fixing it?

Many thanks,

Andy

I have the same problem.

On login i’ll forwarded to the IDP-Login and after successful login i’ll be redirected to the login page of seafile.

I followed the introductions from the manual (https://manual.seafile.com/deploy/shibboleth_config.html)

The Link to Install and Configure Shibboleth Service Provider for Ubuntu isn’t available anymore.

The difference between the Apache configuration are two parts. First of all I use the https configuration. And the second part is the seahub part.

# seahub shibboleth
    #RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
    #RewriteCond %{REQUEST_FILENAME} !-f
    #RewriteCond %{REQUEST_URI} !^/Shibboleth.sso
    #RewriteRule ^(.*)$ /seahub.fcgi$1 [QSA,L,E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    #
    # seahub
    #
   SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
   SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
   ProxyPass / fcgi://127.0.0.1:8000/

Only the default apache configuration is working. If I change it to the seahub shibboleth part I only get an 404 error. I don’t understand the seahub shibboleth Rewrite Rule. Where is the redirect from port 8000 to root.

How to configure seahub is the same as manual.

Best regards
Wiesel82