I noticed that a shared link (to a library or a file) is not persistent while connecting via shibboleth, whereas ity is persistent while connecting while a local account.
If you connect from a shared link, you are send to the home page of seahub.
Cold you check this on your side (it is quite unconvenient) ?
Do you mean that you get redirected to the homepage after having logged in?
I see a similar behaviour when I want to access the “System Administration” menu and have to log in again (“sudo”). The workaround there is to just access the menu again after that and then it works.
Yes, we get a similar behaviour, but with a shared link redorected to the home page, you can’t access to the file in one click, you have to browse groups, librarires and so on.
Unfortunately, it did not fix the problem. I can do more tests if you need.
I removed seahub cache and restarted apache and seahub without fastcgi.
I’m not sure that Javascript is a good solution while working with shibboleth onto Proxy.
regards,
Gautier
I pasted it in /seahub-data/custom/templates/registration/, and the modification is shown in the source of the login page.
I restarted apache to apply the config update (wsgi).
I does not work at all.
To let you know, there is also a shib login in the admin Web UI while the session of the admin has ended. Do i have to update another file ?
regards