Jump to:
| Project: | Boost |
| Version: | 6.x-1.16 |
| Component: | Caching logic |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Can anyone help, or point me in a sensible direction?
I have a site that uses the Shibboleth module for user authorization and subsequent login. Boost is great for the dominant audience of anonymous users, and for the few user accounts that use the conventional D6 /user/login they only get served live content (as expected). However, Boost is not recognizing users who are logged in via Shibboleth, and after login, they get served [anonymous] cached pages if they already exist, ie, Boost treats them as anonymous.
I'm only a few weeks into using Boost, so am still playing around with the settings. However, am I on to a loser here? Is getting Shib to work with Boost too big a redesign? Or should I start nosing around in the code to see if I can apply a small patch?
Would welcome any thoughts...
Comments
#1
This might be related - #627958: Change shib_auth module weight to give it higher precedence to avoid login issues
Boost uses hook_user() to set a cookie saying your logged in so don't serve content from the cache. If you wish to do a quick hack to get this working, wherever the code is that says your now logged in, in the shibboleth module, place a call to boost_user('login'); or boost_user('logout');
This appears to be an issue with that module not boost. The module should be calling module_implements() but I don't think it is.
#2
Thanks @mikeytown2 - I can see a quick hack coming now.
I've been racking my brain for days, as page rendering seems to be inconsistent since I had Boost running. Sometimes a browser refresh is all that is needed - and the 'live' page will appear to a logged-in user; but frequently it's not that simple.
In the interests of maintainer sanity, I've closed this article in the Boost queue, and may follow this up in the shib_auth queue.